Re: Long timeouts on logging out/shutting down

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18/7/22 10:18, Mike Wright wrote:
On 7/17/22 16:26, Stephen Morris wrote:
On 18/7/22 04:41, Patrick O'Callaghan wrote:
On Sun, 2022-07-17 at 19:14 +0200, Francis.Montagnac@xxxxxxxx wrote:
Hi.

On Sun, 17 Jul 2022 17:39:35 +0100 Patrick O'Callaghan wrote:
Actually, according to systemd-system.conf(5), it looks like the
proper place to do this is with a file under
/usr/lib/systemd/system.conf.d, similar to the old rc.d init
files.
Presumably that will avoid the setting being overwritten by a new
install.
Well, that was a bust. Turns out that you do have to edit the
standard
file(s) to have any effect.
It works for me.

Did you specified the [Manager] tag in the drop-in file ?
Of course not. That would mean I had actually understood the manual.

Example:

## Weird: systemd seems to uses internally a ...USec name for that
systemctl show --property=DefaultTimeoutStopUSec
DefaultTimeoutStopUSec=1min 30s

mkdir /usr/lib/systemd/system.conf.d
echo -e '[Manager]\nDefaultTimeoutStopSec=5s' >
/usr/lib/systemd/system.conf.d/99-stop-fast.conf

systemctl daemon-reload

systemctl show --property=DefaultTimeoutStopUSec
DefaultTimeoutStopUSec=5s
I'll try it that, thanks.
Just a silly question on this, what shows this issue? I'm running KDE and the config files in /etc listed in a prior thread have the same settings for the timeout as listed, albeit every setting in those files are prefixed with a "#", does this mean they are all commented out or is the "#" required syntax, but I am not seeing the issue, or at least not like it randomly used to be.


Typically that means these are the default values.  Uncomment and change the value to customize it.
Thankyou, I wasn't sure if this used the reverse logic I've seen in other config files where if you removed the "#" the statement got ignored.

regards,
Steve

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux