SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 28 | October | 2001 ]

>> Next Message >>


Date: Sun, 28 Oct 2001 00:13:10 PDT
From: Peter Skye <pskye@peterskye.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.
=====================================================

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

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


>> Next Message >>

Return to [ 28 | October | 2001 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.