Date: Thu, 13 Jul 2006 18:33:19 -0400 (EDT) From: Chris Hill <chris@monochrome.org> To: Mike Jeays <mj001@rogers.com> Cc: Jean-Paul Natola <jnatola@familycareintl.org>, Andy Greenwood <greenwood.andy@gmail.com>, "Peter A. Giessel" <pgiessel@mac.com>, freebsd-questions@freebsd.org Subject: RE: TIME loss Message-ID: <20060713182906.I43814@tripel.monochrome.org> In-Reply-To: <1152829240.809.110.camel@chaucer.jeays.ca> References: <3A85D7EF44E1C744BF6434691F5659E997548B@www.fcimail.org> <20060713172641.Q43814@tripel.monochrome.org> <1152829240.809.110.camel@chaucer.jeays.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Jul 2006, Mike Jeays wrote: > On Thu, 2006-07-13 at 17:35 -0400, Chris Hill wrote: >> [...] To sync the clock on boot, you can add >> >> ntpd_sync_on_start="NO" # Sync time on ntpd startup, even if offset is high >> >> ...to /etc/rc.conf. > Wouldn't 'ntpd_sync_on_start="YES"' work better? Or is it a very > non-intuitive parameter? Refer to > http://www.qnd-guides.org/qnd-ntpd.html You're right, of course. I sit corrected. Maybe that's why my clock is wrong :^) Good link, BTW. -- Chris Hill chris@monochrome.org ** [ Busy Expunging <|> ]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060713182906.I43814>