It seems that Bruce is not connected to an external NTP server since he said he has to manually update his NTP server to change to DST.
That's definitely not the way things are intended to be, and in my opinion (and my experience), regardless of the possible advantages, running things contrary to the way the rest of the world does always comes back and bite you. Sometimes, it's even better to be wrong with the rest of the world than to be right, but to be the only one to know :-) Maybe I should not be opening that can of worms... Didier John Ackermann N8UR wrote: > Didier Juges said the following on 01/20/2007 11:43 AM: > > >> 2) If the NTP server is set to localtime, which is not a standard time >> server configuration, then this server is only useful on the local net >> but you don't need to mess with the clients. If you have a large local >> net with disparate machines, that may be easier to manage. >> >> It seems you are doing 2), not that there is anything wrong with that. >> Just be careful when a guest plugs his laptop into your network, he may >> not be configured that way and will get the wrong time. >> > > Well, one big problem with that is that you will not be able to get time > from any external NTP server because they will think you are X*3600 > seconds away from the correct time. Setting system clocks to local time > can be done on a self-contained network, but on the Unix side it goes > against The way Things Are Expected To Work. > > John > _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
