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
start it, but then it's too late)?
[snip]
So I would suggest
rc-update add net.eth0 default
Slightly off...
ifplugd is used to bring a network connection up/down when the
network device is plugged in or unplugged. So the OP doesn't want
net.eth0 starting at boot automatically because the cable might not
be plugged in at the time.
Unfortunately that's as much as I know about ifplugd. I do know
that the gentoo network scripts will ensure that the "provide net"
flag is defined that ntp-client relies upon to do it's thing.
What I don't know is how integrated ifplugd is with the gentoo
network scripts, if it too ensures the "provide net" flag is
specified. Nor do I know if, upon cable switching from eth0 to
eth1 for example, the network services that were previously tied to
eth0 would be restarted to now use eth1...
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 scripts to figure
out how to get the timing to work right...
ifplugd seems to have the ability to do whatever you want when the
interface gets link and loses it, couldn't you just add the ntp-
client call in the actions script (as specified in the /etc/conf.d/
ifplugd file?). I just installed ifplugd today, so am by no means an
expert...
--
gentoo-user@gentoo.org mailing list
