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 dstarusers.org have also been removed. 73 de Darren G7LWT 2009/12/14 Kent Johnson <w7...@narri.org> > > > 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 > > www.narri.org > > > > >
