On 2016-07-27 19:54, Michał Zegan wrote:
> Hello.
>
> There is, it seems, a problem with the hardware clock. That is, the
> systemd does not care about it. Neither systemd nor udev rules set the
> system time using the hardware clock.
Strictly speaking, systemd does at bootup what hwclock used
Currently I use hwclock command directly for situations like that (with
dragonboard, pi etc) , it's automated using chef.
On Jul 27, 2016 10:55 AM, "Michał Zegan" wrote:
> Hello.
>
> There is, it seems, a problem with the hardware clock. That is, the
> systemd does
Hello.
There is, it seems, a problem with the hardware clock. That is, the
systemd does not care about it. Neither systemd nor udev rules set the
system time using the hardware clock.
From what I know, if the clock is a cmos rtc, the kernel always sets
time during bootup. In any other case, it
Thanks Adrien.
yes it is same issue.
Could you please let me know how did you resolve this ?
I was browsing through sytemd code and my theory is that by the time
properties changed signal is being prepared to be sent, service has already
gone through mutiple state changes or the unit is unloaded
For the moment, I gave up writing a nice script based on DBus's
PropertiesChanged events, and I made a temporary dirty script which poll
the service status. I did not solve that in a good way.
--
Adrien BESNARD
2016-07-27 11:47 GMT+02:00 Pradeepa Kumar :
> Thanks Adrien.
>
I may be wrong, but it sounds like the issue I encoutered here:
https://github.com/systemd/systemd/issues/3390. I also wanted to build a
service monitoring tool :)
Cheers,
--
Adrien BESNARD
2016-07-26 11:24 GMT+02:00 Pradeepa Kumar :
> Hi
> ActiveState property with value