On Fri, 13 May 2005, Joan Picanyol i Puig wrote:
> * Tony Arcieri <[EMAIL PROTECTED]> [20050513 03:21]:
> > Is there some easy way to reverse this order, so svscan is started first and
> > jails started afterward?
>
> Follow the author's instructions, and put this line into /etc/rc.local:
>
> csh
* Tony Arcieri <[EMAIL PROTECTED]> [20050513 03:21]:
> Is there some easy way to reverse this order, so svscan is started first and
> jails started afterward?
Follow the author's instructions, and put this line into /etc/rc.local:
csh -cf '/command/svscanboot &'
qvb
--
pica
_
On 5/12/05, Tony Arcieri <[EMAIL PROTECTED]> wrote:
> Is there some easy way to reverse this order, so svscan is started first and
> jails started afterward?
Rename the svscan.sh script to 000svscan.sh so that it shows up first
in a directory listing and is run before the jail scripts
(jail-x.x.x
I'm running dnscache and tinydns on the parent system, started through
daemontools with /usr/local/etc/rc.d/svscan.sh. I also have a number of
jails configured in /etc/rc.conf
My problem is the jails contain instances of Apache, qmail, and other DNS
dependent services which need tinydns running o