src-test/sbin/init/init.c, branch release/7.2.0

MFC: revs 1.64-65: style(9)

2008-03-16T07:52:22Z

Patches to allow one to allow one to specify a directory to chroot to.

2007-02-04T06:33:13Z

This includes support for running a script to setup that directory. The kenv variables init_chroot and init_script control this behavior, and are documented in loader(8) that's about to be committed (along with the other variables like init_path...). Submitted by: Oliver Fromme Reviewed by: myself, jhb (earlier versions)

Reparent the process that executes the window= command from the ttys

2006-06-08T14:04:36Z

to the init. This prevents zombies from being accumulated. PR: bin/64198 Tested by: Eugene Grosbein Approved by: kan (mentor) MFC after: 1 month

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

Make WARNS=6 happy with our init(8):

2005-01-11T14:34:29Z

- Use more ``const''s where suitable. - Define strk() as a static function in global scope. This avoids the "nested extern declaration" warnings. - Use static initialization of strings, rather than referring string constants through char *. - Bump WARNS from 0 to 6.

Turns out that revision 1.52 was a bad idea. It broke the long

2004-09-28T04:22:55Z

standing ability to list a non-existant device in /etc/ttys to keep it from dying. This is a documented feature of init(8): The init utility can also be used to keep arbitrary daemons running, automatically restarting them if they die. In this case, the first field in the ttys(5) file must not reference the path to a configured device node and will be passed to the daemon as the final argument on its com- mand line. This is similar to the facility offered in the AT&T System V UNIX /etc/inittab. So rather than fix the man page to 'break' this feature, back out the change. At the time this change was made, people felt that the spamage from getty was annoying on headless consoles. Andrew Gallatin noted: > Most of my machines are headless without video cards and use a serial > console. With devfs this means that /dev/ttyv[1-N] do not exist and > getty bitches like this: > > Sep 26 11:00:11 monet getty[543]: open /dev/ttyv1: No such file or directory and we went off and applied this hack rather than fixing getty to sleep forever when it gets an unknown device, as was Andrew's other suggestion. Since it breaks things, I'm off to do that instead.

Remove advertising clause from University of California Regent's license,

2004-04-09T19:58:40Z

per letter dated July 22, 1999. Approved by: core, imp

Fixed misspellings of 0 as NULL.

2004-03-11T10:01:12Z

Fix the case where one goes from zero to more than zero items enabled

2003-12-05T04:28:03Z

in /etc/ttys. Before this fix, once the count of active services reaches 0, one could never restart any more without a reboot. Steve Passe did the leg work on this patch. After he found the fix, we discovered that an identical fix had been made to NetBSD. Approved by: re@ Approval tool: peril sensitive sunglasses

Back out the previous commit, since there could be dire consequences if

2002-12-17T21:23:36Z

/etc/rc were accidentally executed (as requested by other committeers).