Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 31 Mar 2005 10:46:52 +0200 From: Andrzej Wisniewski To: cygwin AT cygwin DOT com Subject: ntpdate -q problem after daylight saving changes (v3.2 beta) Message-ID: <20050331084652.GB24448@axit.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.1i Hello I have installed a Cygwin ntpdate ver. 3.2 (beta) on Windows 2000 Server. There I have a problem after change time on our server with daylight saving mechanism. I'm in GMT+01:00 zone and few days ago our clock was changed from 02:00am to 03:00am o'clock. From this moment command : ntpdate -q xx.xx.xx.22 started to return wrong diff (3600sek) between local Windows server time and our NTP server time. It seems like ntpdate -q try to compare windows +01h time with basic NTP server time - without +01h (I have a ntp-4.1.2-0 on my Linux server machine). --- $ ntpdate -dq xx.xx.xx.22 server xx.xx.xx.22, port 123 stratum 3, precision -17, leap 00, trust 000 refid [xx.xx.xx.1], delay 0.0256, dispersion 0.0010 transmitted 4, in filter 4 reference time: c5f62e83.de9fadaf Thu, Mar 31 2005 9:08:35.869 originate timestamp: c5f62e97.e1815a07 Thu, Mar 31 2005 9:08:55.880 transmit timestamp: c5f63ca7.000e0000 Thu, Mar 31 2005 10:08:55.000 filter delay: 0.0256 0.0256 0.0256 0.0256 0.0000 0.0000 0.0000 0.0000 filter offset: -3599.12 -3599.12 -3599.11 -3599.11 0.00000 0.00000 0.00000 0.00000 delay 0.0256, dispersion 0.0010 offset -3599.1213086 C:\cygwin\home\nagios\ntpdate: ntpdate version=3.2 (beta); Wed Sep 8 19:37:02 GMT 1993 (1) transmit(xx.xx.xx.22) receive(xx.xx.xx.22) transmit(xx.xx.xx.22) receive(xx.xx.xx.22) transmit(xx.xx.xx.22) receive(xx.xx.xx.22) transmit(xx.xx.xx.22) receive(xx.xx.xx.22) transmit(xx.xx.xx.22) C:\cygwin\home\nagios\ntpdate: step time server xx.xx.xx.22 offset -3599.1213086 ------- I think that "transmit timestamp" should be a "originate timestamp" value and then the problem would not be exist. Is it can be a problem in implementation ? Did anybody observe similary problem or can check it in your system ? Regards -- Andrzej -- 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/