Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <200408111217.i7BCHkh27476@mail.herma.de>
From: Andreas Baetz <lac01 AT web DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: running cygwin sshd results in unreliable timer on w2003 DC
Date: Wed, 11 Aug 2004 14:17:23 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The problem is not sshd related.

It only occurs at a certain ESX server, and there it can be reproduced on different VMs (not only DCs).
The slowdown of the local clock can be triggered by a simple "sleep 100" (with cygwin).

BTW: sleep from the reskit doesn't slow down the clock.

My apologies for falsely "accusing" sshd.

Andreas


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