Date: Sat, 8 Jul 2000 12:29:24 -0700 (PDT) From: "Eugene M. Kim" <ab@astralblue.com> To: Adam <bsdx@looksharp.net> Cc: "Andrey A. Chernov" <ache@FreeBSD.ORG>, "David O'Brien" <obrien@FreeBSD.ORG>, 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-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc rc.shutdown Message-ID: <Pine.BSF.4.20.0007081154230.84816-100000@home.astralblue.com> In-Reply-To: <Pine.BSF.4.21.0007080516111.407-100000@turtle.looksharp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
That sounds like a good idea, provided that it will be gone after a reasonable heads-up grace period. One scenario might be: * In FreeBSD 4.1: - Add a `# start|stop' line to every startup script in ports. - Make rc / rc.shutdown aware of non-conforming scripts which are likely to be homemade ones or ones from previous port/package installation. The rc scripts should treat the old scripts in the compatibility mode, and should explicitly say something like: starting local daemons: vn. Local package initialization: apache pgsql Samba squid mixer. ---------- IMPORTANT NOTICE ---------- The following startup script(s) does not conform to the start/stop argument conventions which took effect starting from 4.1-RELEASE: /usr/local/etc/rc.d/samba.sh /usr/local/etc/rc.d/mixer.sh The system is currently treating them in compatibility mode, but they should be modified or upgraded per the guideline found at http://www.freebsd.org/newstartupscripts.html as soon as possible. The compatibility mode may be removed in upcoming releases, and then all old scripts will be noninteroperable with the system. Once they are upgraded, you won't see this notice again. ----------- END OF NOTICE ------------ * In FreeBSD 4.2: - Remove the compatibility mode from rc and port startup scripts. On Sat, 8 Jul 2000, Adam wrote: | On Sat, 8 Jul 2000, Andrey A. Chernov wrote: | | >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. | | Can't we run a grep -l "somethinghere" /usr/local/etc/rc.d/* at | shutdown and only run those scripts which contain a reasonable indication | of supporting the stop feature? A quick hack to make this work would be | to put a comment in the .sh scripts which ports install which grep would | find and wordy enough that someone could look at a FreeBSD supplied .sh | and say Oh! I see how to make mine work like that. Even just: | | # I support start|stop | | | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe cvs-all" in the body of the message | -- Eugene M. Kim <ab@astralblue.com> "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." 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?Pine.BSF.4.20.0007081154230.84816-100000>