On Fri, 09 Sep 2005 18:13:47 -0400, Dave Nebinger wrote:
I'm willing to gues that in the OP's case the ifplugd is not setting
the provide net flag correctly and/or it is setting the flag before a
cable is actually connected. In any case it's probably down dirty
with the gentoo networking
What determines the order that things in rc-update (/etc/init.d) start?
I run ifplugd, and I notice that (as the title says), ntp-client is starting
before net.eth0 and therefore can't find the pool.ntp.org site (of course).
/etc/init.d/ntp-client shows
depend()
{
before cron portmap
On Fri, 2005-09-09 at 14:08 -0700, Daevid Vincent wrote:
What determines the order that things in rc-update (/etc/init.d) start?
I run ifplugd, and I notice that (as the title says), ntp-client is starting
before net.eth0 and therefore can't find the pool.ntp.org site (of course).
Look at
Daevid Vincent schreef:
What determines the order that things in rc-update (/etc/init.d) start?
I run ifplugd, and I notice that (as the title says), ntp-client is starting
before net.eth0 and therefore can't find the pool.ntp.org site (of course).
/etc/init.d/ntp-client shows
depend()
So shouldn't it wait till the network has started and I have an IP
address
from ifplugd?
Well, isn't the problem here that the network isn't being requested to
start (until ntp tries to make a connection, which of course attempts to
start it, but then it's too late)?
[snip]
So I would
On Sep 9, 2005, at 5:13 PM, Dave Nebinger wrote:
So shouldn't it wait till the network has started and I have an
IP address
from ifplugd?
Well, isn't the problem here that the network isn't being
requested to
start (until ntp tries to make a connection, which of course
attempts to
6 matches
Mail list logo
