Hello Clint,
Tuesday, October 23, 2007, 5:36:15 PM, you wrote:
CP> From what I have read in this thread, it looks like only one guy
CP> prefers the old timed and rdate tools. A few are even telling him he is
CP> giving bad advice when promoting the usage of these tools. Henning
CP> mentioned that rdate and timed are pretty much useless and others have
CP> said that timed is obsolete. So why don't we remove them from the source
CP> tree?I've never suggested (or mentioned) the timed.
Of course I was talking about the "-n" mode of rdate (as a replacement to
ntpdate like Paul de Weerd was suggesting in this thread).
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).--
Best regards,
Boris mailto:boris@twopoint.com
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
