Date: Tue, 14 Dec 2010 16:53:49 -0800 From: Chuck Swiger <cswiger@mac.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Dan Allen <danallen46@airwired.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: ntpd fails on boot Message-ID: <D668F0D8-F871-4B40-B8CE-29DDBAEE9A73@mac.com> In-Reply-To: <20101215004739.GB56065@icarus.home.lan> References: <F211F762-1572-4509-9A3D-807E0595C1CD@airwired.net> <7B9EB743-7C87-42AF-85DE-C05352E4A429@mac.com> <20101215004739.GB56065@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 14, 2010, at 4:47 PM, Jeremy Chadwick wrote:
[ ... ]
>> Change the REQUIRE line in /etc/rc.d/ntpd to indicate whatever dependency you need to have so that your network connection is up before ntpd tries to run. "man rcorder" is informative....
>
> It's not that simple.
Shrug-- if there is *unmentioned* additional complexity, well, no doubt you're correct.
Another alternative might be to switch to launchd, which is more of a capability-based system which stops and starts services more dynamically, including upon notification that an intermittent network connection is presently active and usable. ("rc NG" is quite capable on it's own right, but a lot of the flexible behavior of a Mac laptop dealing with suspend/resume, network drops and resumes, etc comes from launchd architecture.)
Regards,
--
-Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D668F0D8-F871-4B40-B8CE-29DDBAEE9A73>