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()
> {
> before cron portmap
> need net
> use dns logger
> }
>
> 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)?
Look here:
>
> locutus ~ # rc-update show
> net.ath0 |
> net.eth0 |
> net.eth1 |
> net.eth2 |
> net.lo | boot
> net.ppp0 |
> net.wlan0 |
net.lo starts at boot, but no other network service is being started at all.
> netmount | default
> nscd |
> ntp-client | default
and then here's ntp-client, which needs the network that isn't started.
On the other hand, here's my setup:
rc-update show
net.eth0 | default
net.lo | boot
Both net.lo and net.eth0 are being started, so by the time we get to
ntp-client | default
it's capable of making a connection to the server.
So I would suggest
rc-update add net.eth0 default
might solve your problem.
Holly
--
gentoo-user@gentoo.org mailing list
