Issues with setting the timeofday
Rick Altherr
raltherr at google.com
Fri Jul 8 02:52:36 AEST 2016
If ntpd or systemd-timesyncd is running, this makes perfect sense. Linux
maintains current time in the kernel. The hardware RTC is only used to
load an initial time at boot and is written during shutdown. When an NTP
daemon is running and an NTP server is reachable, it will adjust the
kernel's current time to match NTP time. I believe with timesyncd, it
simply steps time instead of slewing like ntpd does.
What are you trying to accomplish? There is likely a way to do it if you
can describe what you want to have happen.
On Thu, Jul 7, 2016 at 6:06 AM, Vishwanatha Subbanna <vishwanath at in.ibm.com>
wrote:
> hey Joel,
>
> Here is what I am seeing on one the Barreleye box that is running
> "4.4.12-openbmc-20160606-1 : kernel". I can see that time gets set but
> reverts immediately. Syncing what's in hwclock does not have any effect
> too. Any thoughts ?
>
> root at barreleye:~# date -s '2016-12-25 12:34:56' ; hwclock -w
> Sun Dec 25 12:34:56 UTC 2016
>
> root at barreleye:~# date
> Thu Jul 7 13:07:37 UTC 2016
>
> root at barreleye:~# hwclock -r
> Sun Dec 25 12:35:01 2016 0.000000 seconds
>
> root at barreleye:~# hwclock -s
>
> root at barreleye:~# date
> Thu Jul 7 13:07:52 UTC 2016
> root at barreleye:~#
>
> Thanks
>
>
> -------------------------------------------------------------------------------------
> Thanks and Regards,
> Vishwanath.
> Advisory Software Engineer,
> Power Firmware Development,
> Systems &Technology Lab,
> MG2-6F-255 , Manyata Embassy Business Park,
> Bangalore , KA , 560045
> Ph: +91-80-46678255
> E-mail: vishwanath at in.ibm.com
>
> ----------------------------------------------------------------------------------
>
> _______________________________________________
> openbmc mailing list
> openbmc at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160707/845bc4e0/attachment.html>
More information about the openbmc
mailing list