Date: Sat, 8 Jul 2000 02:09:17 -0700 From: "Andrey A. Chernov" <ache@freebsd.org> To: David O'Brien <obrien@FreeBSD.org> Cc: Peter Wemm <peter@netplex.com.au>, Robert Watson <rwatson@FreeBSD.org>, Sheldon Hearn <sheldonh@uunet.co.za>, Brian Somers <brian@Awfulhak.org>, Thomas Gellekum <tg@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc.shutdown Message-ID: <20000708020917.A26528@freebsd.org> In-Reply-To: <20000707231906.B88142@dragon.nuxi.com>; from obrien@FreeBSD.org on Fri, Jul 07, 2000 at 11:19:06PM -0700 References: <rwatson@FreeBSD.org> <200007070044.RAA03203@netplex.com.au> <20000707231906.B88142@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 07, 2000 at 11:19:06PM -0700, David O'Brien wrote: > On Thu, Jul 06, 2000 at 05:44:33PM -0700, Peter Wemm wrote: > > 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. > > I'd rather make "stop" required in ports and call with it in current. > Then a 'HEADS UP' to -current. The added functionally is just too nice > not to have. The problem is not for ports, many people have hand-made local scripts in /usr/local/etc/rc.d which knows nothing about start/stop. I prefer /usr/local/etc/shutdown.d for programs which require it than damaging many systems at once by restarting local scripts on shutdown. -- Andrey A. Chernov <ache@nagual.pp.ru> http://ache.pp.ru/ 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?20000708020917.A26528>