/etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before starting server.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Ubuntu) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: ntp
Ubuntu: 8.04.1
ntp: 1:4.2.4p4+
Despite other comments on here that ntpdate should be run from ifup scripts there is still a fundamental issue.
If due to failures such as #114505 not bringing up ntpd correctly if the clock drifts you have to ifdown, ifup an interface. On a major server thats just plain ridiculous...To fix the ntp daemon I have to pull down an ENTIRE network interface and stuff every service that is running on that interface - simply to fix ntpd.
The alternative is that I have to either recognise and issue and then
/etc/int.d/ntp stop
ntpdate-debian
/etc/init.d/ntp start
again silly - because an /etc/init.d/ntp restart should work - the point of running NTP is it syncs.
Therefore I propose that the /etc/init.d/ntp script is patched to include running of 'ntpdate-debian' during startup of the ntp server. This is a far more fail-safe method of working instead of forcing the admin to have to remember to run ntpdate-debian in case the clock has drifted excessively.
Changed in ntp (Ubuntu): | |
status: | Incomplete → Triaged |
status: | Triaged → Confirmed |
tags: | added: patch |
The patch I use is:
--- ntp 2008-10-24 22:11:49.000000000 +0100
log_ failure_ msg "user \"$RUNASUSER\" does not exist"
exit 1
start- stop-daemon --start --quiet --oknodo --pidfile $PIDFILE --startas $DAEMON -- -p $PIDFILE -u $UGID $NTPD_OPTS
log_end_ msg $?
+++ ntp 2008-10-24 21:34:00.000000000 +0100
@@ -37,6 +37,7 @@
fi
+ ntpdate-debian
;;