SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Tue, 13 May 2003 20:17:10 PDT7
From:	Sheridan George <s-geo@usa.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: More on setting clock from startup.cmd

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

There is a whole bunch of chatter that I don't understand. I've been
using a registered version of OS2NTPD for several years with excellent
service. I have a shadow of it in the Startup folder causing it to
start and run in the background. I have 6 time servers in my cfg_data
list and when I check it is using three to five of them.

It checks for the TZ variable in config.sys and sets the clock including
adjusting for daylight savings time. In the past I have gone to a
command prompt and set the time to some arbitrary time. Within a few
minutes the system clock is back where it should be; meaning OS2NTPD is
making only small adjustments to the clock. (I just checked it; there
was an adjustment of +0.016 second; 4 min later no adjustment needed; 4
min after that no adjustment needed. BTW, OS2NTPD starts by polling time
servers every 16 seconds. Whenever that RTC is brought to within one
tick (31.5 ms) the polling time is extended by two times until it
reaches 256 seconds.)

According to the manual OS2NTPD adjusts the RTC by resetting the divider
chain at the appropriate time. So, Peter, why is Daytime needed?

The only thing that OS2NTPD does not do is serve time to other computers
on a local LAN like Time868 does. For me this is not a handicap because
no one computer is always on here. It is no trick to have OS2NTPD on
all machines and let each one grab time from the net when that machine
is on.

What in the world am I missing?

Sheridan

Peter Skye wrote:

>=====================================================
>If you are responding to someone asking for help who
>may not be a member of this list, be sure to use the
>REPLY TO ALL feature of your email program.
>=====================================================
>
>I posted my startup.cmd file a couple of days ago.
>
>One of the commands in it runs Daytime which gets the "atomic clock"
>time over the Internet and accurately sets the hardware clock on the
>motherboard.
>
>I've been meaning to add some additional time server sites to Daytime
>because the various Internet clocks (technically Network Time Protocol
>servers, or NTP servers) sometimes aren't available which means the
>motherboard clock doesn't get set.
>
>So yesterday I added some more time server sites to make sure at least
>one of them is available when startup.cmd runs. Here is the updated
>section of my startup.cmd:
>
> daytime tick.usno.navy.mil
> daytime time-b.nist.gov
> daytime utcnist.colorado.edu
> daytime clock.psu.edu
>
>There are a _lot_ of NTP servers. If you want the best accuracy try to
>pick ones that are close to you to minimize lag time (you can check the
>routing and delay with tracerte, or just the delay with ping).
>
>Remember that once Daytime sets your clock from startup.cmd your clock
>will still "drift" a bit because it has nothing to synchronize to (my
>machines have drifts of anywhere between 20 seconds and two minutes over
>a 24 hour period). If you run a clock synchronizing program in a window
>after your bootup is done your clock will always be correct. I use
>OS2NTPD; one thing I like about it is that it uses a lot of different
>NTP servers and averages their values which gives a higher accuracy.
>Another OS2NTPD benefit is that it continues to keep the motherboard
>clock synchronized even when you aren't connected to the Internet by
>using a software phase locked loop to figure out the necessary
>compensation per unit of time. A third thing I like about OS2NTPD is
>that its resolution is 1/60 second which is much better than the others
>I've looked at.
>
>- Peter
>
>
>
>=====================================================
>
>To unsubscribe from this list, send an email message
>to "steward@scoug.com". In the body of the message,
>put the command "unsubscribe scoug-help".
>
>For problems, contact the list owner at
>"rollin@scoug.com".
>
>=====================================================
>
>
>
>
>
>

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 13 | May | 2003 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.