Date: Tue, 8 Oct 2002 09:48:42 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/sbin/init init.c Message-ID: <20021007234842.GK495@gsmx07.alcatel.com.au> In-Reply-To: <XFMail.20021007184451.jhb@FreeBSD.org> References: <20021007214019.GA80107@gsmx07.alcatel.com.au> <XFMail.20021007184451.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-Oct-07 18:44:51 -0400, John Baldwin <jhb@FreeBSD.org> wrote: >> This means that I could include the following line in /etc/ttys >> proxy2 "/usr/local/libexec/proxy2 -f /usr/local/etc/proxy.ports" none on >> and init would happily run my program (because /dev/proxy2 does not >> exist), restarting it if it died. > >That seems to be a really gross hack. Arbitrary daemons have nothing >to do with setting up ttys. I wouldn't mind if init grew the ability >to handle arbitrary daemons via some other method that was less of a >hack and more of intended design. Would that be acceptable? I agree that using /etc/ttys in this way is somewhat of a hack - but it is a very useful hack and I don't think there's any other way to ensure that an arbitrary process automatically restarts. I'd be happy if init grew this ability in a more controlled manner - though I'm not quite sure how to achieve it. (System V has /etc/inittab but we don't want to grow the rest of the baggage that comes with /etc/inittab). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021007234842.GK495>