>> just run sntp via cron every hour. > > Danger, bad, evil and multiple varieties of not good. running sntp every hour > on the whatever is considered very not good.
>why's that? > >@ http://linux.die.net/man/1/sntp > >"sntp can be used as a SNTP client to query a NTP or SNTP server and >either display the time or set the local system's time (given suitable >privilege). It can be run as an interactive command, in a cron job or >as a daemon. It can be run as a daemon to provide a SNTP server for >other clients. NTP is the Network Time Protocol (RFC 1305) and SNTP is >the Simple Network Time Protocol (RFC 2030, which supersedes RFC >1769)." > > seems like it's not a problem. Because everyone (and their dog) comes up with that as a solution. They all set it to run at the top of the hour. Then at the top of the hour, NTP servers get hammered by by all the little single requests that the admin won't notice. think of it as the network equivalent of the death by a thousand cuts. Also if you clock is really fast there is the possibility that it will be set back far enough that the cron job will be run twice. twice the load now at the old price. I could stick something like 'rm -rf /' in my crontab. That doesn't make right. keep in mind your OS hands you enough rope to hang yourself, that doesn't mean you should. (/rant mode="rabid") JamesB192 ---- Msg sent via CableONE.net MyMail - http://www.cableone.net _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
