Re: [9fans] timesync is slow to set the time after boot

[Richard Powell <richard@powell.name>]

David,

If there are problems reading the clock on the first pass, maybe we 
could just wait one second between passes instead of one minute. (Or 
even zero seconds if you think that's safe enough.).

Thanks for looking into this.
Richard



diff -c timesync.org timesync.c.tsecs0
*** timesync.c.org        Fri Mar 14 19:42:32 2003
--- timesync.c.tsecs1   Sun Mar 16 00:05:10 2003
***************
*** 344,349 ****
--- 344,350 ----
                         break;
                 case Rtc:
                         s->stime = sample(rtctime);
+                       tsecs = 1;
                         break;
                 case Utc:
                         s->stime = utcsample();
***************
*** 385,391 ****
                 diff = s->stime - s->ltime;
                 if(diff > 10*SEC || diff < -10*SEC){
                         // we're way off, just set the time
!                       secs = MinSampleSecs;
                         settime(s->stime, 0, 0, 0);
                 } else {
                         // keep a running average of the error.
--- 386,392 ----
                 diff = s->stime - s->ltime;
                 if(diff > 10*SEC || diff < -10*SEC){
                         // we're way off, just set the time
!                       tsecs = secs = MinSampleSecs;
                         settime(s->stime, 0, 0, 0);
                 } else {
                         // keep a running average of the error.



David Presotto wrote:
> I stopped ignoring the first sample.  It made some difference since the
> first sample is usually perverted a bit by the system starting up.  However,
> it really doesn't help to have a wrong time for a minute.   Thanks powell.
>