Date: Mon, 11 Jun 2007 09:28:26 -0400 From: Matt Pounsett <matt@conundrum.com> To: freebsd-questions@freebsd.org Subject: rc.d NETWORKING dependancy not waiting for network to be up Message-ID: <1ACC527A-E8B3-42C6-9F71-F10B0B6F77A4@conundrum.com>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It looks like the NETWORKING dummy dependancy doesn't actually cause
the its dependants to wait for networking to be up, but simply for
interfaces to be configured. I'm wondering if this is actually
intended, or if it's an unavoidable design flaw, or what?
I'm noting on my systems that ntpdate and ntpd are trying to start
before the network is actually reachable, and therefore both have
issues starting. ntpdate is unable to sync the clock properly before
ntpd starts, and ntpd doesn't seem to ever be able to sync to a time
server if it starts trying to contact one before the network is fully
up... and needs to be restarted after boot in order for it to work
properly.
I'm working around the issue by sticking a 20 second delay into /etc/
rc.d/NETWORKING (this is probably way more than necessary, but I'm
allowing for a large margin of error) which seems to fix my problem,
but is obviously not ideal.
Any background or suggestions related to this from anyone?
Thanks,
Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFGbU39ae4z2vjbC8sRAgq9AJ46G/zvz4W4kCBTSdxdoC85ZUW4nwCg0iLX
EW4HDKBsWEMw8LT4EPmnwnY=
=wExI
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ACC527A-E8B3-42C6-9F71-F10B0B6F77A4>