On 29/12/2023 08:26, Valerio Vanni wrote:
Il 29/12/2023 00:12, Charles Curley ha scritto:
That may work, but by putting the script in /usr/lib/systemd, you run
the risk of it being clobbered on the next update to systemd. Better to
put it in /etc/systemd/system-sleep/. Files in /etc/systemd over-ride
their analogs in /usr/lib/systemd, so it should continue to work. You
may need to do a "systemctl daemon-reload".
This way it doesn't work.
systemd-sleep(8) does not mention /etc/systemd/system-sleep/
I am a bit puzzled by the following:
https://www.freedesktop.org/software/systemd/man/latest/systemd-sleep.html
Note that scripts or binaries dropped in /usr/lib/systemd/system-sleep/
are intended for local use only and should be considered hacks. If
applications want to react to system suspend/hibernation and resume,
they should rather use the Inhibitor interface.
https://www.freedesktop.org/wiki/Software/systemd/inhibit/
From my point of view dealing with D-Bus just to unload a kernel module
is inconvenient. It is not an application that is started before suspend
and should be running after resume. I am curious what is the recommended
way for this particular use case.
