Re: Watchdog problem

[Vito Caputo <vcaputo@xxxxxxxxxxx>]

On Sat, Sep 07, 2019 at 07:41:13PM +0200, Mikael Djurfeldt wrote:
> On Sat, Sep 7, 2019 at 7:26 PM Chuck Wolber <chuckwolber@xxxxxxxxx> wrote:
> 
> > On Sat, Sep 7, 2019 at 10:17 Mikael Djurfeldt <mikael@xxxxxxxxxxxxx>
> > 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.
> >>>
> >>
> >> I think this sounds like what I want. How do I do this?
> >>
> >
> > I do not have your system up to be precise, but the simplest way is to
> > create an override copy of the whole unit file. This means you miss out on
> > changes to the unit made in upstream updates, but that is on you.
> >
> > You would usually find the unit file by looking for the first comment line
> > from the command - systemctl cat logind.service (or whatever the unit is
> > named). Then copy that file to /etc/systemd/system and make all the edits
> > you want.
> >
> > Then reload systemd (systemctl daemon-reload) to make it aware of the
> > changes.
> >
> 
> 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.
> 
> What I really would want to know now is where the documentation is for
> WatchdogSec such that I don't need to guess like this.
> 

See the systemd.service(5) man page.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel