Date: Thu, 16 Dec 1999 10:02:38 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) Message-ID: <99Dec16.095420est.40348@border.alcanet.com.au> In-Reply-To: <12188.945290928@critter.freebsd.dk>; from phk@critter.freebsd.dk on Thu, Dec 16, 1999 at 07:48:48AM %2B1100 References: <199912152044.NAA63531@harmony.village.org> <12188.945290928@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Dec-16 07:48:48 +1100, Poul-Henning Kamp <phk@critter.freebsd.dk> wrote:
>And we don't really need YAD when we have init hanging around doing
>nothing for its keep anyway...
I beg to differ. To quote init(8):
The role of init is so critical that if it dies, the system will reboot
itself automatically. If, at bootstrap time, the init process cannot be
located, the system will panic with the message ``panic: init died
(signal %d, exit %d)''.
This suggests that init needs to be very robust - which generally
translates to `small and well audited'. Non-core functionality
(which IMHO includes devd) really belongs in another process.
Looking at the development side, it's also painful to debug init -
another reason for leaving it alone.
>and at the same time I wouldn't mind if init were taught to keep
>important programs running, things like sshd, inetd, syslogd and
>similar should be restarted if they die.
It can do that now. Add the following lines to /etc/ttys:
sshd "/usr/local/sbin/sshd" none on
inetd "/usr/sbin/inetd -Ww" none on
syslogd "/usr/sbin/syslogd" none on
(This ability has always been present, but is now documented).
Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99Dec16.095420est.40348>