Date: Tue, 17 Jan 2012 10:25:36 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Jos Backus <jos@catnook.com> Cc: Doug Barton <dougb@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: Importing djb's public domain daemontools? Message-ID: <86boq2smsv.fsf@ds4.des.no> In-Reply-To: <CAETOPp1OYqu2UuaqXdrnCGXYKq%2B=cz_DP3K%2BmHo0zprYo=kpdQ@mail.gmail.com> (Jos Backus's message of "Mon, 16 Jan 2012 22:32:02 -0800") References: <CAETOPp2Wcww1_fPonru0c6XoX%2BAV_HWoGZKiEMvmY50a5%2ByxRQ@mail.gmail.com> <4F14E291.5090803@FreeBSD.org> <CAETOPp1z0TJecz8kjDvf7trEOS5eogrcqEtDveUYzN=J-SvDNQ@mail.gmail.com> <4F1502CD.90409@FreeBSD.org> <CAETOPp1OYqu2UuaqXdrnCGXYKq%2B=cz_DP3K%2BmHo0zprYo=kpdQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jos Backus <jos@catnook.com> writes: > I want/need a solution that works in (nearly) all cases and is devoid of > complex code trying to track state that is already represented elsewhere = in > the system (the process table and the parent/child process > relationship). Please show me the complex code required to handle pidfiles. > I want a solution that can reliably handle a crashing server that > doesn't clean up its pidfile That's a strawman. Whatever tool you use needs to be able to handle stale pidfiles anyway. > I want a unified control interface for the services running on a box, > a la launchd or what have you. So extend service(8) to support enabling / disabling services through /etc/rc.conf.d/<servicename>. Probably no more than an afternoon's work. > This isn't about religion but about missing base system functionality > - the ability to reliably control services running on a box. The onus is on you to show that we don't already have that. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86boq2smsv.fsf>