blm@ingwaz.pair.com wrote: > Firstly I am new to the Debian Way of doing things. Welcome! :-) > In short, I reckon the ntp stuff needs more documentation especially > about the debian specific stuff. Is this valid? Yes. But I assume you are running stable. If sid ever gets out the door you will see some significant updates and improvements in NTP. > that the server configuration comes from /etc/default/ntpupdate. > Now I understand that /etc/default is an important dir tree for > debian configuration but it would have been nice to go man ntpupdate > and see /etc/default/ntpupdate in the FILES section of a man page > for ntpupdate. Does anyone agree? In the latest ntp configuration the file is /etc/default/ntpdate. So your problem is already fixed and will be in the next Debian release. > Anyway it turns out that the ntp stuff on my debian machine was talking > NTPv2 and the server NTPv3 so my client was being ignored. To update > the clock off the windows server I had to use: > > /usr/bin/ntpupdate -o 3 time.domain.com > > Hopefully I haven't wasted anyones time, No. But unfortunately bugs like these need to be checked against the latest versions which will be released in the next release. Debian stable is just that, stable. It only changes with the next release. Once you start talking about changing what is there then you have to go to unstable and develop there. One of the reasons I know about the ntp changes is that I was tracking down a different problem. Checking against unstable I could see much activity there. Bob
Attachment:
pgp39XC8srJ0q.pgp
Description: PGP signature