Date: Thu, 30 Mar 1995 14:51:55 -0800 From: Paul Traina <pst@shockwave.com> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: phk@ref.tfs.com (Poul-Henning Kamp), ache@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-etc@freefall.cdrom.com Subject: Re: cvs commit: src/etc/etc.i386 rc.i386 Message-ID: <199503302252.OAA04182@precipice.shockwave.com> In-Reply-To: Your message of "Thu, 30 Mar 1995 13:37:14 PST." <199503302137.NAA06580@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In BSD this has always been done by root editing /etc/rc.local, I never did like things that automagically went and f*cked around in /etc, I consider that evil and ugle. USG does exactly what Paul suggested, but as we've seen with ~ and .bak files, it is dangerous. They have an rc.<runlevel>.d directory for each run level and files with the names: <S|U><priority 00-99><name> so it executes all the system stuff first (lower numbered stuff runs first) followed by all of the user stuff every time you change run levels. I agree with you 100% for system stuff as the ordering for this stuff is always a MAJOR pain in the ass. However, it would be nice if we could handle rc.local-ish things this way. It would be great if when you install httpd, as an example, you could install a file /etc/rc.local.d/httpd which is a shell script for starting up httpd at boot. Would you consider the following compromise? for file in rc.local.d/* l do echo $file | \ egrep -s "~$|.bak$|.orig$|.rej$|<other nastys>" || \ sh $file done
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503302252.OAA04182>