Re: Making startup order static

2006-09-11 Thread Alex Zbyslaw
White Hat wrote: 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

Re: Making startup order static

2006-09-11 Thread White Hat
--- Alex Zbyslaw [EMAIL PROTECTED] wrote: [...] I believe 6.1 uses rcorder for scripts from /usr/local/etc/rc.d, in which case you might be able to create local patches in the relevant ports which added appropriate e.g. # BEFORE: # PROVIDES: # REQUIRE: lines to force the order you

Re: Making startup order static

2006-09-11 Thread RW
On Sunday 10 September 2006 19:11, White Hat wrote: FreeBSD 6.1 I need to keep several programs starting in a particular order. ... The problem is that every time I update these programs the rc.d startup file is modified which destroys the changes I have made. I've got around this problem

Making startup order static

2006-09-10 Thread White Hat
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

RE: Making startup order static

2006-09-10 Thread White Hat
--- Martin Werner [EMAIL PROTECTED] 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

RE: Making startup order static

2006-09-10 Thread J.D. Bronson
At 02:02 PM 9/10/2006, White Hat wrote: --- Martin Werner [EMAIL PROTECTED] 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,

Re: Making startup order static

2006-09-10 Thread Duane Hill
On Sunday, September 10, 2006 at 7:02:09 PM, White confabulated: --- Martin Werner [EMAIL PROTECTED] 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

RE: Making startup order static

2006-09-10 Thread White Hat
--- J.D. Bronson [EMAIL PROTECTED] wrote: 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 ? I had considered that approach. The problem is if the program is updated it will will write a

Re: Making startup order static

2006-09-10 Thread ajm
On Sun, Sep 10, 2006 at 11:11:36AM -0700, White Hat wrote: 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

Re: Making startup order static

2006-09-10 Thread White Hat
--- Duane Hill [EMAIL PROTECTED] wrote: [...] I also had the same scenario with order in startup. That was rectified by setting up one script to start each of the items in order. I am assuming that you removed the scripts that you called from the rc.d directory. What transpired when you

Re: Making startup order static

2006-09-10 Thread Duane Hill
On Sunday, September 10, 2006 at 9:46:13 PM, White confabulated: --- Duane Hill [EMAIL PROTECTED] wrote: [...] I also had the same scenario with order in startup. That was rectified by setting up one script to start each of the items in order. I am assuming that you removed the

Re: Making startup order static

2006-09-10 Thread White Hat
--- Duane Hill [EMAIL PROTECTED] wrote: [...] No. I believe I used the startup script for sa-spamd as a starting point. I'm sure others could be used as a starting point as well. I'm still in the learning process. That way I could remove the ones from the rc.conf that I wanted to