From owner-freebsd-current Wed Dec 15 15: 9: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2A65114CED for ; Wed, 15 Dec 1999 15:09:03 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id AAA12875; Thu, 16 Dec 1999 00:07:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) In-reply-to: Your message of "Thu, 16 Dec 1999 10:02:38 +1100." <99Dec16.095420est.40348@border.alcanet.com.au> Date: Thu, 16 Dec 1999 00:07:49 +0100 Message-ID: <12873.945299269@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Dec16.095420est.40348@border.alcanet.com.au>, Peter Jeremy writes : >On 1999-Dec-16 07:48:48 +1100, Poul-Henning Kamp 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. Well, there are a lot of chicken & eggs issues with devd, which may skew that a bit, but lets examine that when we get there. >>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). Yes, but apart from the highly unintuitive name "/etc/ttys" any process which involves edititing a file and signalling a process has a big potential for races. I would prefer if the lines could be added to /etc/ttys somewhat like: sshd "/usr/local/sbin/sshd" none ondemand And then we could telinit -on sshd telinit -off sshd or similar. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message