src/sbin/init/init.8, branch upstream/10.1.0

mdoc: terminate quoted strings.

2012-03-26T15:18:14Z

Reviewed by: brueffer

Make init(8) slightly more robust when /dev/console is missing.

2012-03-14T16:22:09Z

If the environment doesn't offer a working /dev/console, the existing version of init(8) will simply refuse running rc(8) scripts. This means you'll only have a system running init(8) and nothing else. Change the code to do the following: - Open /dev/console like we used to do, but make it more robust to use O_NONBLOCK to prevent blocking on a carrier. - If this fails, use /dev/null as stdin and /var/log/init.log as stdout and stderr. - If even this fails, use /dev/null as stdin, stdout and stderr. So why us this useful? Well, if you remove the `getpid() == 1' check in main(), you can now use init(8) inside jails to properly execute rc(8). It still requires some polishing, as existing tools assume init(8) has PID 1. Also it is now possible to use use init(8) on `headless' devices that don't even have a serial boot console.

Move utmpx handling out of init(8).

2012-02-11T20:47:16Z

This has the following advantages: - During boot, the BOOT_TIME record is now written right after the file systems become writable, but before users are allowed to log in. This means that they can't cause `hidden logins' by logging in right before init(8) kicks in. - The pututxline(3) function may potentially block on file locking, though this is very rare to occur. By placing it in an rc script, the user can still kill it with ^C if needed. - Most importantly: jails don't use init(8). This means that a force reboot of a system running jails will leave stale entries in the accounting database of the jails individually.

- change "is is" to "is" or "it is"

2011-10-16T14:30:28Z

- change "the the" to "the" Approved by: lstewart Approved by: sahil (mentor) MFC after: 3 days

init(8): Document that login(1) is now responsible for recording logouts.

2011-01-23T14:54:45Z

init(8) only uses utmpx for recording reboots and shutdowns.

Remove stale references to utmp(5) and its corresponding filenames.

2010-01-21T17:25:12Z

I removed utmp and its manpage, but not other manpages referring to it.

Fix typo: effected -> affected

2007-01-02T09:12:37Z

Submitted by: Gordon Stratton

-mdoc sweep.

2005-11-18T10:36:29Z

Fix system shutdown timeout handling by again supporting longer running

2005-09-15T13:16:07Z

shutdown procedures (which have a duration of more than 120 seconds). We have two user-space affecting shutdown timeouts: a "soft" one in /etc/rc.shutdown and a "hard" one in init(8). The first one can be configured via /etc/rc.conf variable "rcshutdown_timeout" and defaults to 30 seconds. The second one was originally (in 1998) intended to be configured via sysctl(8) variable "kern.shutdown_timeout" and defaults to 120 seconds. Unfortunately, the "kern.shutdown_timeout" was declared "unused" in 1999 (as it obviously is actually not used within the kernel itself) and hence was intentionally but misleadingly removed in revision 1.107 from init_main.c. Kernel sysctl(8) variables are certainly a wrong way to control user-space processes in general, but in this particular case the sysctl(8) variable should have remained as it supports init(8), which isn't passed command line flags (which in turn could have been set via /etc/rc.conf), etc. As there is already a similar "kern.init_path" sysctl(8) variable which directly affects init(8), resurrect the init(8) shutdown timeout under sysctl(8) variable "kern.init_shutdown_timeout". But this time document it as being intentionally unused within the kernel and used by init(8). Also document it in the manpages init(8) and rc.conf(5). Reviewed by: phk MFC after: 2 weeks

Moved descriptions of securelevels from init(7) to security(7).

2005-09-03T17:16:00Z

Files used both "securelevel" and either "secure level" or "security level"; all are now "security level". PR: docs/84266 Submitted by: garys Approved by: keramida MFC after: 3 days