From owner-freebsd-hackers Tue Nov 17 19:42:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10658 for freebsd-hackers-outgoing; Tue, 17 Nov 1998 19:42:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com ([207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10579 for ; Tue, 17 Nov 1998 19:41:58 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id TAA28972; Tue, 17 Nov 1998 19:38:46 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id TAA29464; Tue, 17 Nov 1998 19:38:25 -0800 (PST) Message-ID: <19981117193824.A29415@thought.org> Date: Tue, 17 Nov 1998 19:38:24 -0800 From: Gary Kline To: Jamie Lawrence , Jacques Vidrine , Nik Clayton Cc: hackers@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? References: <19981117235348.41074@nothing-going-on.org> <19981115235938.22908@nothing-going-on.org> <19981117210138.03327@nothing-going-on.org> <199811172241.QAA00519@spawn.nectar.com> <19981117235348.41074@nothing-going-on.org> <199811180255.UAA01561@spawn.nectar.com> <3.0.5.32.19981117190738.00b04bd0@204.74.82.151> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3.0.5.32.19981117190738.00b04bd0@204.74.82.151>; from Jamie Lawrence on Tue, Nov 17, 1998 at 07:07:38PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think the big win here is a common framework for handling what can > become highly complex daemon start/stop procedures. One that I've > ended up doing is database daemons. Example: you want to kill msql > for whatever reason. It serves some fast CGIs that in turn provide > functionality to web users at large. A stop procedure for this daemon > involves killing the fcgis, killing the DB daemon, moving a "service > unavailable" page into the docroot (or some other mechanism for end > user notification), and possibly other tasks. Right now, everyone who > builds a script for this does it differently. With a rc.d framework, > this sort of problem becomes much more standardized, as admins will > tend to build them into that framework. > > I think the real tradeoff is between homegrown complexity that > often is under documented and homegrown complexity that at least > follow conventions that are easy to follow. > > This is one of the few places I actually prefer Solaris to FreeBSD > (run state madness notwithstanding). > The commonality is the major win, I think. Either the BSD world moves to the SysV model, or Sun and SCO and AIX and Linux should adopt our model. If _we_ do it at least it will be done correctly, by wizard hackers. gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message