From owner-freebsd-arch@FreeBSD.ORG Tue Jan 17 09:25:37 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C62FA106566C; Tue, 17 Jan 2012 09:25:37 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 870598FC0C; Tue, 17 Jan 2012 09:25:37 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 8006D6B1A; Tue, 17 Jan 2012 09:25:36 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 601B4874A; Tue, 17 Jan 2012 10:25:36 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jos Backus References: <4F14E291.5090803@FreeBSD.org> <4F1502CD.90409@FreeBSD.org> Date: Tue, 17 Jan 2012 10:25:36 +0100 In-Reply-To: (Jos Backus's message of "Mon, 16 Jan 2012 22:32:02 -0800") Message-ID: <86boq2smsv.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Doug Barton , freebsd-arch@freebsd.org Subject: Re: Importing djb's public domain daemontools? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 09:25:37 -0000 Jos Backus 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/. 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