On Sun, Mar 25, 2007 at 10:54:55PM +0200, Luca Corti wrote: > On Fri, 2007-03-23 at 15:14 -0600, Shane Harbour wrote: > > Look at the "-S" option and see if that's what you want. > > I think you mean "-s". Yes I use it but still the clients report they > won't sync because of the server not being synced.
Have you measured the time from ntpd startup until it logs `clock is now synced' in the log? On the same machine, I see anywhere from 10 minutes to about 1 hour. In normal cases, machines acting as time servers are always on. If it takes less than an hour for ntpd to sync, and then it's up for months at a time then there's little problem. If you want to turn on a computer and have it fetch some times from the network and report that it's synced... well, that's not accurate. A big, full-blown, complex thing like xntpd won't do it, either. If you don't really care what time it is, but want all your local computers to have the same time (or very, very close) there are other ways such as timed(8). Then you can have a computer using ntpd, and synced or not it can be a timed master for your network. -- Darrin Chandler | Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
