You did not post your override.conf file for inspection, so it is hard to
tell.
Did you remember to do a systemctl daemon-reload after you added your
override.conf?
..Ch:W..
On Tue, Aug 25, 2020 at 4:27 PM Richard Hector
wrote:
> Hi all,
>
> I've got the common warning:
>
> /lib/systemd/system
On Wed, Feb 12, 2020 at 10:31 AM Xogium wrote:
> I am wondering about how to best implement a mechanism to recreate a
> specific
> filesystem in case of the slightest data corruption done to it.
>
I am not sure if there is a built-in method to do what you are asking, but
I think you could
use a
On Sat, Sep 7, 2019 at 10:41 Mikael Djurfeldt wrote:
>
> Oh, now I see what you meant by "override".
>
> I set WatchdogSec=0 and got no complaints when reloading, so I guess this
> is how I disable the watchdog.
>
Indeed. But for future reference, keep in mind that not everything can be
overridde
On Sat, Sep 7, 2019 at 10:17 Mikael Djurfeldt wrote:
>
> In any case, you can get rid of the watchdog altogether with an override.
>> Granted, you will not detect logind hangs, but that is probably not a huge
>> concern for your particular use case if you want to stay logged in all the
>> time.
>
On Sat, Sep 7, 2019 at 06:12 Mikael Djurfeldt wrote:
>
%< Snip %<
>
> When the host has gone to sleep and wakes up again, I get logged out from
> my gdm session. It starts out like this:
>
> Sep 7 13:23:58 hat kernel: [82210.177399] 11:23:58.337557 timesync
> vgsvcTimeSyncWorker: Radical guest
Is it generally considered bad form to start up a service unit from within
an application?
I have been trying to keep everything under the direct control of systemd,
but I ran in to a problem that I am not quite sure how to resolve and still
keep systemd in control of everything.
I have a daemon
