Date: Fri, 11 Jul 1997 15:01:31 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: aflundi@lundin.abq.nm.us (Alan Lundin) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/init.d/ Message-ID: <199707112201.PAA25774@phaeton.artisoft.com> In-Reply-To: <199707111120.FAA01337@lundin.abq.nm.us.> from "Alan Lundin" at Jul 11, 97 05:20:40 am
next in thread | previous in thread | raw e-mail | index | archive | help
> I guess I don't see what the problem with the > current system is. Currently you can have one > script (assuming you have NFS mounting it amoung > N machines) that says: > > case `hostname` in > $SERVER) <startup httpd> > ;; > esac > > where if it is moved to /etc/rc.d, then you must > maintain N scripts, AND you stand more of a chance > that those scripts will get clobbered on the next > OS upgrade. What if I *want* to clobber the scripts for upgraded facilities when I upgrade the facility? What if I want to upgrade some facilities, but not others? I guess you'd have me editing up my rc file so that I couldn't upgrade without editing it again (big hassle). The other side of the coin is, when I install the HTTP server, I want startup and shutdown sequences placed in my startup and shutdown sequences, automatically, without me having to edit an rc file there, either. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707112201.PAA25774>