On Wed, Oct 24, 2007 at 10:47:45AM -0500, Boris Goldberg wrote: | May be it makes sense to set "-ncv" as a default behavior of rdate, but | there is should be a way to synchronize time without running a demon (don't | understand why are people so aggressive about that) if you don't need | up-to-second synchronization (in my case modern hardware goes less than a | second off per day, and really old hardware - less than 10 seconds).
The problem here is the jump in time. You repeat a second or more (if you have to jump back) or skip some (if you jump forward). This may not be a problem for you in particular, but is considered bad in general. Another issue is the fact that the server you're syncing to may not be perfectly sync'ed itself. Or maybe there's some (assymmetrical) delay in the network. This may make time on your machine somewhat off (this isn't as big a problem as the previous, IMO). And it's totally unneccessary, simply run ntpd and be done with it. It solves all the problems with syncing every once in a while, and as I indicated in my earlier mail, I don't see any of the problems with running another daemon on my machines that you described. It's small, uses proven security techniques and is still reasonably simple. But hey, if using rdate from a cron is your thing, dont let me get in your way. I used to do this before we had OpenNTPD too, since I wasn't really happy with ntp.org's daemon. If you're not really happy with OpenNTPD, more power to you ! But I dont think it's a good practice to do so, so suggesting it to others on this mailinglist will get you some replies from opponents of your solution... Cheers, Paul 'WEiRD' de Weerd -- >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] http://www.weirdnet.nl/