From owner-freebsd-bugs Mon Mar 5 0:20: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B107037B719 for ; Mon, 5 Mar 2001 00:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f258K3l54225; Mon, 5 Mar 2001 00:20:03 -0800 (PST) (envelope-from gnats) Date: Mon, 5 Mar 2001 00:20:03 -0800 (PST) Message-Id: <200103050820.f258K3l54225@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Andy Farkas Subject: Re: conf/25514: ntpdate_flags in /etc/defaults/rc.conf should be set to "-b" Reply-To: Andy Farkas Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/25514; it has been noted by GNATS. From: Andy Farkas To: cjohnson-pr@palomine.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: conf/25514: ntpdate_flags in /etc/defaults/rc.conf should be set to "-b" Date: Mon, 5 Mar 2001 19:15:23 +1100 (EST) > >Description: > > According to the ntpdate man page, ntpdate should be run with -b when > run from a startup file at boot time. This causes the time to be stepped > rather than slewed. The man page also says, by default, if the clock is in error more than 0.5 second it will step, rather than slew, the time. What I see as a problem is in /etc/rc.network where it pipes the output of ntpdate to /dev/null. If ntpdate fails to step the clock, and the clock is way out of sync, then ntpd (if enabled) will also fail to work. /etc/rc.network should be smarter and check return codes when starting ntpdate and/or ntpd. Should it pipe the output to logger(1)?? -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message