Date: Sat, 12 Jul 1997 22:11:37 -0600 (MDT) From: Alan Lundin <aflundi@lundin.abq.nm.us> To: Terry Lambert <terry@lambert.org> Cc: freebsd-hackers@freebsd.org Subject: Re: /etc/init.d/ Message-ID: <199707130411.WAA04700@lundin.abq.nm.us.> In-Reply-To: Terry Lambert <terry@lambert.org> "Re: /etc/init.d/" (Jul 11, 3:01pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 11, 3:01pm, Terry Lambert wrote: > Subject: Re: /etc/init.d/ > > > 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? That's why you put the above code in /usr/local/etc/rc.d/httpd.sh (I guess I didn't say that did I?) > 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). No, my mistake for not stating that the code would go into /usr/local/etc/rc.d/***.sh rather than /etc/rc.*. --alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707130411.WAA04700>