SCOUG-HELP Mailing List Archives

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

Date:	Mon, 29 Oct 2001 21:02:12 PDT
From:	Sheridan George <s-geo@usa.net >
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.
=====================================================

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.
> =====================================================
>
> > Peter Skye wrote:
> > >
> > > os2ntp ... takes a while to settle down
>
> Sheridan George wrote:
> >
> > That is what I use and it took only 10 min. to
> > get to "no local clock correction necessary".
>
> Hmm. I kept a log file running and it shows 1-1/2 hours to settle down
> to a one-minute error and an additional 15 minutes to get to "no local
> clock correction necessary". Last year was similar.
>
> By chance did you have a log file running? It's not a default, you have
> to press the F11 key to start it. I'd like to compare your log to
> mine. (Or did you stay up and watch it?)

No but I wish I had to turn on the log. I turned on my computer after church to set my watch so I
could set the rest of the clocks (only set one alarm clock for wake up). I was interested in how long
it would take for the computer's clock to become correct so I came back to the office in about 5+
min. I was surprised to find the computer clock at the correct time. So I set my watch.

The only thing that gave me a hint that all was not settled yet was the seconds on my watch. My watch
forces me set the seconds first then the rest of the stuff. So my routine is to set the seconds then
the hour and minutes and then go back to the seconds for a touch up. When I did that the minutes were
off by two. Grrr. How did I do that? Set the minutes again and back to the seconds and off again.
What?!

Brought NTPD to the foreground. It was adjusting the clock by about 4 seconds every 10 seconds or
so. OK, it's not done yet. Went off and read some e-mail. When I came back all was settled. (OK,
OK maybe it was 15-20 minutes from turn on 'till setteled. I boast a lot, ya know.)

That is the best log I have. In 6 mos. I'll try to remember to turn on the logger.

>
> Also, the TZ setting from CONFIG.SYS might have an impact. Here's mine:
>
> SET TZ=PST8PDT,4,1,0,3600,10,-1,0,7200,3600
>
> What does yours look like?

Oh, come on, man! I'm a simple, country engineer. All of that time domain stuff is too technical for
me. Mine is simply: SET TZ=PST+8PDT

Don't bother to ask. I don't know why I put the + there. I do know it's working and I'm not removing
it!!

BTW, my version is: OS2_NTPD V1.2 Jun 21 1998

Sheridan

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

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 [ 29 | 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.