On Mon, 2022-08-15 at 15:21 +0200, francis.montag...@inria.fr wrote:
> 
> On Mon, 15 Aug 2022 12:19:20 +0100 Patrick O'Callaghan wrote:
> 
> > This solution has simply stopped working. The default timeout is
> > indeed
> > set as described:
> 
> > $ systemctl show --property=DefaultTimeoutStopUSec
> > DefaultTimeoutStopUSec=5s
> 
> Have you checked also for systemctl --user ?
> 

$ systemctl --user show --property=DefaultTimeoutStopUSec
DefaultTimeoutStopUSec=1min 30s

Aha! Now where do I change that?

> > (note the strange and undocumented "USec" rather than "Sec", which
> > you
> > have to use to get the value despite "Sec" being used in setting
> > the
> > property)
> 
> I have seen that and though as you that it was not documented, but it
> is.
> 
> Go first in man systemd.directives, then search for it:
> 
>         TimeoutStopUSec
>            org.freedesktop.systemd1(5)
> 
> then search for it in the man of org.freedesktop.systemd1: around the
> line
> number 1956 ... :-)
> 
>    This reflects that fact that internally the service manager deals
> in
>    microsecond units only

I see. However it doesn't really explain why I get:

$ systemctl show --property=DefaultTimeoutStopSec
$

i.e. no output. IOW the parameter I explicitly set in the config file
is listed as not being set, and there's no indication that the other
parameter is the one I should be looking at. Had I not seen your
earlier post on this, I would simply think that there was something
wrong with how I was setting it (discounting the '--user' issue).

This is unbelievably obscure.

poc
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to