boiled down to one command
authorChris Koeritz <fred@gruntose.com>
Tue, 22 May 2018 17:13:01 +0000 (13:13 -0400)
committerChris Koeritz <fred@gruntose.com>
Tue, 22 May 2018 17:13:01 +0000 (13:13 -0400)
currently working on ubuntu for time synch of client, so leaving it like this.

infobase/configuration/cron/time_synch.crontab

index 77e41d5c698013224729bf93d3fe9b74945008f8..f59270620a163c867b71d5d42975d30dc68e1da9 100644 (file)
@@ -2,13 +2,15 @@
 #[time synch]
 
 # standard to synch to local machine.
-#0,4,8,12,16,20,24,28,32,36,40,44,48,52,56 * * * * /usr/sbin/sntp -P no -r greendragon &>>/tmp/${CRONUSER}-cron-time_synch.log
-#or
-0,4,8,12,16,20,24,28,32,36,40,44,48,52,56 * * * * /usr/bin/rdate -s -n greendragon &>>/tmp/${CRONUSER}-cron-time_synch.log
-# -n is nntp which may not work with govt servers.
+
+##############
+
+# synchronize time/date with our nearest time server.
+*/4 * * * * /usr/sbin/ntpdate greendragon &>>/tmp/${CRONUSER}-cron-time_synch.log
+
+##############
 
 # one machine on the network uses this version, to synch externally.
-#0 0,4,8,12,16,20 * * * /usr/sbin/sntp -P no -r time.nist.gov &>>/tmp/${CRONUSER}-cron-time_synch.log
-#or
 0 0,4,8,12,16,20 * * * /usr/bin/rdate -s time.nist.gov &>>/tmp/${CRONUSER}-cron-time_synch.log
+#hmmm: is above still correct?