Message: previous - next
Month: March 2018

Re: [trinity-users] Incorrect digital clock time

From: William Morder <doctor_contendo@...>
Date: Sat, 31 Mar 2018 06:01:19 -0700

On Saturday 31 March 2018 02:08:12 Rolf Schmidt wrote:
> Hi,
> > The additional info is that logging out and logging back in -- which is
> > something I rarely do; I often go weeks without doing so, but I happened
> > to do it today -- "fixed" the problem.
> It seems that your clock will set at login time perhaps you set/use
> different timezones for the clocks.
> I usually use ntpd to sync my clock via internet. But make shure your
> clock has less then 1 or 2 minute differenc to utc.
> Best is:
> - stop the utp daemon
> - use ntpdate to correct you clock
> - perhaps use 'hwclock -w' to adjust the hardware clock too.
> - start ntpd again.
> Now the clock will be adjusted continusly (I don't know the length of
> the intevall between two updates).
> Rolf

You might find these two webpages to be useful:
This page gives a bash script: 
date -s "$(curl -sI|grep -i 'date:'|
sed -e 's/^.ate: //g')"
I adapted this to use DDG instead of Google; works pretty well. It seems not 
very secure, though, and you may find that now your system time is now a 
little "off" - by several seconds or more, compared to other online devices - 
although maybe it's better than off by an hour. 

At the end of the page I've cited above is a link to another bash script: