Hi,
But Ossama has some ideas:
--------------------------------------
Patrik's comment assumes that automatic time updates are enabled in Connman
and/or NTP is configured. I don't believe his comment applies when
automatic updates are*disabled*. In that case, the user will set the time
manually. It seems reasonable to expect that time won't be lost at reboot.
Connman probably shouldn't provide a means to set the date and time
*manually* if it isn't going to save that time to the hardware clock.
Without the save to the hardware clock the manual date/time support in
Connman is essentially a redundant and unnecessary D-Bus call around the
settimeofday(2)<http://linux.die.net/man/2/settimeofday> system call.
If desired we can work around this limitation by having the native
date/time setting code set the time in the hardware clock via
/dev/rtc<http://linux.die.net/man/4/rtc>or through
timedated<http://www.freedesktop.org/wiki/Software/systemd/timedated/>.
Either way, the calling process will need the appropriate privilege (
CAP_SYS_TIME<http://man7.org/linux/man-pages/man7/capabilities.7.html>).
-----------------------------------------
Take a look at doc/clock-api.txt: it's set as experimental.
Thus nothing to be excited about.
(With the rise of systemd, part of this API would probably be obsolete.
And if systemd
ends up as unique solution, then probably most of the API would get
scrapped.)
And about hwclock, whatever cron job or proper service (which is usually
the case)
can handle that properly outside of ConnMan.
If your system don't do that, it's a configuration issue there.
Tomasz
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
