From owner-cvs-all Thu Jul 6 23:51:58 2000 Delivered-To: cvs-all@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id ECDE037BCF3; Thu, 6 Jul 2000 23:51:49 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA35556; Thu, 6 Jul 2000 23:50:44 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39657DC3.7D96BEC4@gorean.org> Date: Thu, 06 Jul 2000 23:50:43 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Thomas Gellekum , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc rc.shutdown References: <200007070044.RAA03203@netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Robert Watson wrote: > > > > So, generally, my observation for rc.d scripts was that previously, they > > never even looked at the arguments, so running (whatever) stop will > > actually run additional copies of the service on shutdown, if > > /usr/local/etc/rc.d is not updated. Is this correct? > > I have previously implemented /etc/shutdown.d and /usr/local/etc/shutdown.d > to avoid the confusion about what happens when /etc/rc.shutdown > calls "/usr/local/etc/rc.d/apache.sh stop" and the old apache.sh doesn't > check $1 and starts up instead. Personally I'm a little disappointed that this didn't get more discussion, say on -arch. I think that changing the existing interface is a POLA violation. I would support making a shutdown directory, or potentially even making rc.shutdown more useful so that it calls the scripts for those apps that need them specifically would be better solutions. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message