On Wed, 18.01.17 12:26, lejeczek (pelj...@yahoo.co.uk) wrote:
> hi all
> I'm reading man pages but cannot see whether there is a conflict there,
> a unit:
>
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> TimeoutSec=0
>
> $ systemctl edit
> [Service]
> Restart=on-failure
> RestartSec=90
>
On Tue, 17.01.17 12:29, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> Hello.
>
> I am aware of the fact that systemd relies on the kernel to set system
> clock from hardware clock, and that requires compiling rtc drivers into
> the kernel, not as modules.
> I am also aware that doing it
W dniu 09.02.2017 o 15:52, Lennart Poettering pisze:
> On Tue, 17.01.17 12:29, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
>> Hello.
>>
>> I am aware of the fact that systemd relies on the kernel to set system
>> clock from hardware clock, and that requires compiling rtc drivers into
>>
On Wed, 18.01.17 12:30, lejeczek (pelj...@yahoo.co.uk) wrote:
> sorry guys, I bugged libvirtd but... weirdly, quiet there, so I'm hoping an
> expert here would share a thought.
>
> I've a few VM guest which work/run perfectly fine, I believe, except for
> autostart.
> Configuration of system,
On Thu, 09.02.17 16:14, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> Btw, about the argument that the kernel should set rtc time because of
> wrong timestamps in logs, so I should compile the rtc into the kernel:
> let's compare: if I read rtc time during bootup (and rtc is a module),
>
W dniu 09.02.2017 o 18:49, Lennart Poettering pisze:
> On Thu, 09.02.17 16:14, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
>> Btw, about the argument that the kernel should set rtc time because of
>> wrong timestamps in logs, so I should compile the rtc into the kernel:
>> let's compare:
