Date: Sun, 10 Sep 2006 14:06:20 -0500 From: "J.D. Bronson" <jbronson@wixb.com> To: White Hat <pigskin_referee@yahoo.com> Cc: Martin Werner <bsdml@werner.st>, FreeBSD Users Questions <freebsd-questions@freebsd.org> Subject: RE: Making startup order static Message-ID: <200609101906.k8AJ6KSU011285@shadow.sixcompanies.com> In-Reply-To: <20060910190209.41483.qmail@web34402.mail.mud.yahoo.com> References: <001701c6d509$09392600$2101a8c0@local.werner.st> <20060910190209.41483.qmail@web34402.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 02:02 PM 9/10/2006, White Hat wrote: >--- Martin Werner <bsdml@werner.st> wrote: > > > Hi, > > > > thought about using PROVIDE and REQUIRE keywords > > (see > > /usr/local/etc/rc.d/clamav-clamd.sh resp. > > clamav-freshclam.sh > > > > Maybe you might want to have a look into "man rc" or > > "man rcorder" > > > > Cheers, > > -Martin- > > > > > FreeBSD 6.1 > > > > > > I need to keep several programs starting in a > > > particular order. > > > > > clamav-clamd > > > clamav-freshclam > > > clamsmtpd > > > saslauthd > > > dovecot > > > postfix > > > fetchmail > > > > > By default, they do not start in that order. I >have > > > modified the rc.d files to force them to start in > > > the > > > order specified above. > > < > > > The problem is that every time I update these > > > programs > > > the rc.d startup file is modified which destroys >the > > > changes I have made. This then requires me to > > > recreate > > > the modifications to force the start up order I > > > require. > > > > > > Is there anyway I can achieve this goal in a > > > simplified manner? I thought perhaps there might >be > > > something I could add to the /etc/rc.conf file; > > > however, I have not discovered it. > >Martin, I don't think that you understood what I >meant. Either that or I described it incorrectly. > >I did modify the rc.d files using BEFORE: and >REQUIRE:. That works just fine. The problem is if one >of those files is updated, the rc.d file is >overwritten resulting in the loss of my customization. >I therefore have to manually edit those files again. I >was trying to find someway to circumvent that >procedure. how about putting them in /usr/local/etc/rc.d and then using a numeric to start them 001file.sh 002file.sh or create a script with just one file.sh ? -JD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609101906.k8AJ6KSU011285>