Your message dated Tue, 10 Apr 2007 22:14:02 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#416785: ntpdate: please add hook in crontab
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ntpdate
Severity: wishlist
Tags: patch
It seems that it's not uncommon for the system clock in servers with high
uptimes to go off eventualy. In our tests, we've found that it typicaly
goes off by 1/6912 (~= 15m after 72 days). It would be useful if ntpdate
were run in cron.daily as well, not only via network hooks.
Attached patch enables this by just adding a symlink.
--
Robert Millan
ACK STORM, S.L. - http://www.ackstorm.es/
diff -Nur ntp-4.2.2.p4+dfsg.old/debian/ntpdate.links ntp-4.2.2.p4+dfsg/debian/ntpdate.links
--- ntp-4.2.2.p4+dfsg.old/debian/ntpdate.links 1970-01-01 01:00:00.000000000 +0100
+++ ntp-4.2.2.p4+dfsg/debian/ntpdate.links 2007-03-30 12:30:16.000000000 +0200
@@ -0,0 +1 @@
+etc/network/if-up.d/ntpdate etc/cron.daily/ntpdate
diff -Nur ntp-4.2.2.p4+dfsg.old/debian/rules ntp-4.2.2.p4+dfsg/debian/rules
--- ntp-4.2.2.p4+dfsg.old/debian/rules 2007-03-30 12:25:27.000000000 +0200
+++ ntp-4.2.2.p4+dfsg/debian/rules 2007-03-30 12:41:49.000000000 +0200
@@ -100,6 +100,7 @@
dh_installlogcheck -a
dh_installchangelogs -a
dh_perl -a
+ dh_link -a
dh_strip -a
dh_compress -a
dh_fixperms -a
--- End Message ---
--- Begin Message ---
Submitter is blocking my emails. Apparently not interested in
discussion.
--- End Message ---
