On Aug 11 10:34, Andreas Baetz wrote: > Hi, > > it seems there is a problem with the local clock when running cygwin sshd on a w2003 > DC. > [...] > Problem description: > We have a time server (time1) setup which gets its time from a radio clock. Above > DC1 should synchronize with this server. > With "w32tm /stripchart /computer:time1" the deviation to time1 is constantly shown. > Without sshd started, eveything is fine. No clock difference between DC1 and time1. > After starting sshd, however, the local clock rapidly deviates from time1. It seems > it does slow down, about 0.5 s per sec. > After stopping sshd, the clock deviation vanishes again. > This occurs regardless of the existance of a local time synchronisation mechanism. I > tried the built-in w32time service, > as well as a windows port of ntpd. Neither is capable of syncing the local clock to > time1, if sshd is started.
How likely is it that an sshd should actively affect the clock? I'm wondering if that's a problem with using the same tcp port or something like that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
