I think there's an assumption here that they attempted to contact
Kent.  (He's not hard to find! GRIN!)

I had no problem reaching him at his NARRI e-mail address, which
has worked for me for IRLP admin reasons ever since NARRI
existed.

In fact, I forwarded the list message to him (thinking he might
not be on the mailing list) so he could look at his system, and
before I'd heard back I then saw the announcement that the Admin
"timesync push" was being done.

Kent, check the archives of the list for more info on the
timeline of how it all happened.

Thanks all,
--
  Nate Duehr, WY0X
  [email protected]


On Mon, 14 Dec 2009 10:41 +0000, "Storer, Darren"
<[email protected]> wrote:


Hi Kent,

the time problem on N7ARR has now been resolved.

N7ARR's clock was forward by 10 years, as you can clearly see
from the dsync status that you pasted below; this had some very
negative effects on the trust server, so an emergency time sync
command was pushed to re-sync the server's clock.

Pushing the sync was the last resort as the admin team were
unable to contact you when they were working on the problem and
dplus linking to N7ARR didn't seem to work at the time.

The good news is that not only is the system clock correct now
but the rogue entries in [1]dstarusers.org have also been
removed.

73 de Darren
G7LWT

2009/12/14 Kent Johnson <[2][email protected]>



Darren G7LWT,


You say “N7ARR has a year of 2019” on it s clock. You may want to
contact the N7ARR custodian and let them know! I think that is
better for many reasons.


 I just checked by entering “date” at root and found the GW time
is the same as my PC and cell phone.  I saw no error message when
checking GW history, but did note


                              N7ARR

                       timesync commencing

                       2019-12-13 21:05:00
                       2009-12-13 21:04:44

                 /dstar/scripts/gw_schedule 2.0h

                              N7ARR

                      timesync in 4 Minutes

                       2019-12-13 21:00:02
                       2009-12-13 20:59:46

                 /dstar/scripts/gw_schedule 2.0h


Those who understand “timesync” may want to explain the above.
What imitates “ timesync “ .  Is that a cron?


I saw a time error last week and did a manual timesync including
stop/restart.  I was not aware of further errors and don’t see
any now.  If you do let me know.


Kent W7AOR

Cust N7ARR  and Owner REF014

[3]www.narri.org







References

1. http://dstarusers.org/
2. mailto:[email protected]
3. http://www.narri.org/
4. mailto:[email protected]?subject=re:%20[DSTAR_DIGITAL]%20N7ARR%20clock
5. 
mailto:[email protected]?subject=re:%20[DSTAR_DIGITAL]%20N7ARR%20clock
6. 
http://groups.yahoo.com/group/dstar_digital/message/9288;_ylc=X3oDMTM1ZWlwaWFzBF9TAzk3MzU5NzE0BGdycElkAzIwNTEwNTI2BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAM5Mjg5BHNlYwNmdHIEc2xrA3Z0cGMEc3RpbWUDMTI2MDc4NzI5MQR0cGNJZAM5Mjg4
7. 
http://groups.yahoo.com/group/dstar_digital/members;_ylc=X3oDMTJnNTVwMjNvBF9TAzk3MzU5NzE0BGdycElkAzIwNTEwNTI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2bWJycwRzdGltZQMxMjYwNzg3Mjkx?o=6
8. 
http://groups.yahoo.com/group/dstar_digital;_ylc=X3oDMTJmN201Nm1sBF9TAzk3MzU5NzE0BGdycElkAzIwNTEwNTI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2Z2hwBHN0aW1lAzEyNjA3ODcyOTE-
9. 
http://groups.yahoo.com/group/dstar_digital/post;_ylc=X3oDMTJmNTYzOWFxBF9TAzk3MzU5NzE0BGdycElkAzIwNTEwNTI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNudHBjBHN0aW1lAzEyNjA3ODcyOTE-
  10. 
http://us.ard.yahoo.com/SIG=14kvnl423/M=493064.13814333.13821539.13298430/D=groups/S=1705063108:MKP1/Y=YAHOO/EXP=1260794492/L=/B=8VsHLkSO53c-/J=1260787292183463/K=MKUsWGijbwgUrooIG1AMKg/A=5922843/R=0/SIG=11ckn2mo6/*http://advision.webevents.yahoo.com/green/
  11. 
http://us.ard.yahoo.com/SIG=14k3l5qic/M=493064.13814537.13821737.10835568/D=groups/S=1705063108:MKP1/Y=YAHOO/EXP=1260794492/L=/B=8lsHLkSO53c-/J=1260787292183463/K=MKUsWGijbwgUrooIG1AMKg/A=5898841/R=0/SIG=11kkq36go/*http://advision.webevents.yahoo.com/parentingzone/
  12. 
http://groups.yahoo.com/;_ylc=X3oDMTJlcmE1Z2xmBF9TAzk3NDc2NTkwBGdycElkAzIwNTEwNTI2BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTI2MDc4NzI5MQ--
  13. 
mailto:[email protected]?subject=change%20delivery%20format:%20Traditional
  14. 
mailto:[email protected]?subject=email%20delivery:%20Digest
  15. mailto:[email protected]?subject=unsubscribe
  16. http://docs.yahoo.com/info/terms/

Reply via email to