Re: ports and /etc/rc.d/ [was: Where to put my own startup script]

Tobias Roth wrote:

>>>2) will be very nice. PR 56736 from eik seems to address this very
>>>elegantly. ports that need to be started early can be started directly 
>>>after
>>>the dummy PORTS dependency, all others that do not explicitly request a
>>>specific startup order should be started at the end of rc.d/. this of
>>>course also solves 4).
>>
>>You should not really use PORTS, but whatever you need to run.
> 
> i don't understand what you mean by that. i was just trying to briefly
> describe what your patch from PR 56736 does. maybe i got it wrong?

PORTS is *very* early in the startup process. Most ports require at least
syslogd, so DAEMON or even LOGIN is far more appropriate. If you need
to start early, maybe SERVERS is a good choice.

>>>now, shouldn't racoon be started before mountcritremote? #$%#!#, i think
>>>i just shot myself in the foot. comments please :-) i am sure that can
>>>be fixed elegantly as well.
>>
>>The problem here is that /usr might not be a local filesystem, so touching
>>anything there before mountcritremote is not a really good idea.
> 
> that is exactly what i wanted to say. since racoon might be needed to
> mount remote filesystems, and at the same time possibly being located on
> one, we have a problem.

You can't do that by default. If you want to support this you have to
hand-tune your configuration.

-Oliver