Date: Sun, 9 Jul 2000 13:24:22 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: freebsd-stable@FreeBSD.ORG Subject: Re: HEADS UP: /etc/rc.shutdown calls local scripts now Message-ID: <20000709132421.B394@dialin-client.earthlink.net> In-Reply-To: <20000709143129.B20852@pir.net>; from pir@pir.net on Sun, Jul 09, 2000 at 02:31:29PM -0400 References: <Pine.GSO.4.21.0007091310130.15474-100000@nova.fnal.gov> <20000709143129.B20852@pir.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 09, 2000 at 02:31:29PM -0400, Peter Radcliffe wrote:
> Tim Zingelman <zingelman@fnal.gov> probably said:
> > [ -d ${dir} ] && for script in ${dir}/*.sh; do
> > grep -q "stop.*)" ${script} &&
> >
> > Certainly not guaranteed to catch everything, but much better than
> > nothing IMHO.
>
> How about renaming them ? Leave the existing scripts as .sh, use
> a different suffix for scripts that grok start/stop ?
>
> No changes required for things that don't need to be stopped, no
> slowdown (since nothing is run for scripts that don't need a stop) and
> the things that do want stops are the only thing that have to change ?
>
> Not very clean, admittedly, but it might allow the two to operate
> together until all the old scripts have migrationed, if that was the
> aim.
How about leave the usage of /usr/local/etc/rc.d the same as it is now
and put the sysV style ones in /etc/rc.d or someplace else? In
/etc/rc, there can be "local_startup" and "local_startup_old" lists
that contain the directories which contain each type of script?
--
Crist J. Clark cjclark@alum.mit.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000709132421.B394>