Bug 25514
| Summary: | ntpdate_flags in /etc/defaults/rc.conf should be set to "-b" | ||
|---|---|---|---|
| Product: | Base System | Reporter: | cjohnson-pr <cjohnson-pr> |
| Component: | conf | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.2-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
> >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/ State Changed From-To: open->closed Committed, thanks. |
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. Fix: In /etc/defaults/rc.conf, change ntpdate_flags="" to ntpdate_flags="-b"