SCOUG-HELP Mailing List Archives

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

Date:	Sun, 28 Oct 2001 11:50:13 PDT
From:	Steve Carter <scarter@vcnet.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: nistime ? ntp107 ?

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.
=====================================================

Tick.usno.navy.mil is very slow here. Tock seemed OK,
but quixotic. They're east coast -- USNO is in Washington DC,
although their time servers may not be collocated.
I presume the high traffic load accounts for their current
unavailability. Tycho has been unavaiable for a long while.

time-A.timefreq.bldrdoc.gov has been the most consistent
for me, over the past few years. Norbert Dey, the author
of Time868, recommended it several years ago as being a
west-coast alternative (he's near Portland, OR). I seem to
recall having to add it to time868, as it wasn't included
with the default list of time servers. I've not tried
time-b or time-c, but they are on the NIST list at:

http://www.boulder.nist.gov/timefreq/service/time-servers.html

time.nist.gov [192.43.244.18] at the National Center for
Atmospheric Research in Boulder, CO refuses connection
(maybe it's just to me!).

I use time868f on the OS/2 machine and
AtomicTime II on the windoze machine. I was unable to
get Time868 to act as a time server, one of its included
functions (probably my fault, a networking thing).

-------------

A nice time page to visit is:
http://www.time.gov/

Right now it's interminably slow, 'cause of the time
change, but once the flurry settles down, it should
return to normal again. Worth a peek.

+++++++++++++++
On 10/28/01, Peter Skye wrote, in part:
>
>Since it's clock-change time, I figured I'd check out some of the
>ntp clients I don't use. Two of them (nistime.exe and ntp.exe)
>didn't work properly here:
>
>1. nistime hangs when I run it. The following lines:
>
> nistime -m0 -s0
> nistime -m2 -s0
>
>both "hang" in an OS/2 window. Anybody have any suggestions?
>
>2. ntp (ntp107) doesn't check the TZ environment variable. It set my
>date to GMT time _and_ didn't set the date ahead; thus instead of moving
>me ahead 8 hours it moved me backwards 16 hours. I used this line:
>
> ntp tick.usno.navy.mil
>
>ntp changed something else too and I can't get my time to set properly;
>I'll reboot after I send this message and see if that fixes whatever the
>problem is.
>_____
>
>And the other four that I know of:
>
>3. time868 (time868f) is a PM program with "a bunch of options".
>Seems to work okay.
>
>4. daytime works quite nicely. The following line:
>
> daytime tick.usno.navy.mil
>
>set my clock and took the TZ environment variable into account.
>
>5. I didn't try TimeKeeper/2 (timekeep) because it doesn't appear to
>offer any functionality that the others don't have _and_ it's shareware.
>
>6. os2ntp is what I usually run, and it's still the most accurate. It
>uses a phase locked loop and samples as many time servers as you want,
>which gives extremely high accuracy once it's synchronized. The problem
>with it (and the reason I'm testing the other ntp clients) is that it
>automatically adjusts for Daylight Saving time _but_ the phase locked
>loop takes a while to settle down when it's suddenly hit with a 1-hour
>error (undamped oscillations result).
>
>- 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".

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

Return to [ 28 | October | 2001 ]

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.