This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

running cygwin sshd results in unreliable timer on w2003 DC


Hi,

it seems there is a problem with the local clock when running cygwin sshd on a w2003 DC.

Googling came up with nothing, as well as searching the list archives, so here it goes:

Setup:
Windows 2003 Server as DC (PDC) on a VM with VMware ESX (DC1)
cygwin 1.5.10-3
sshd installed per ssh-host-config with privilege separation, running as domain\sshd_server
sshd-environment "cygwin=ntsec" (tried with "cygwin=ntsec server", too)

sshd runs fine with no functional problems

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.
The CPU load of the server is very low, regardless of the running state of the sshd server.

I'm not sure if the problem lies within sshd, but it can be triggered by starting and stopping the sshd service.

I have running sshd on all of my other windows (NT, w2k, w2003) servers, and none of them shows that problem.
I have another DC (DC2), though, that shows deviations from time to time, but w32time is capable to sync to time1. 
If the sshd service is stopped there, the deviations vanish altogehter, too.

A side question is that why does the clock deviation that accumulated during the run of sshd correct itself,
even if no sync mechanism is running ? I experimented with that a little, too: Setting the clock to be about 5 s from time1,
starting sshd, it deviates (slows down). Stopping sshd, it goes back to those 5 s and stays there.

How do I get the sshd server running without affecting it the local clock on tose DCs ?

Thanks

Andreas Baetz


--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]