[systemd-devel] Perl Net::DBus, org.freedesktop.system1 and inhibitor locks
Michael Hirmke
mh at mike.franken.de
Wed May 25 16:13:00 UTC 2016
Hi Lennart,
thx for your answer!
[...]
>Being just advisory means that a user can shut down the system even if
>a lock is taken, however, the lock is tracked and the expectation is
>that the DE of your choice will still show them first, and ask for
>confirmation to ignore them before you actually use your powers to
>override them. GNOME does this, but I am not sure if your DE does it.
Sorry, I forgot to add information regarding my environment.
I use openSuSE Leap 42.1 with a Plasma 5 desktop.
And at the moment my tests are restricted to run my script and then send
the system to sleep myself - so no other user is involved for the
moment.
>"systemctl poweroff" will show these locks in a similar way too, but
>not for the root user.
>> - I am not able to close the file descriptor in the pre block of the
>> signal handler. Whenever I try, I get an error, that the descriptor
>> is closed.
>This suggests something else closed the fd for you?
Yes, but who or what might that be?
As I wrote above - at the moment I'm the only one using the system and I
have no idea, what component might fiddle with my file descriptors.
Do you have any hint, how I could find that out / debug it?
And there is the fact, that the lock is still in the list of inhibitors.
As far as I understand the docs, the entry should be gone when the fd is
closed.
>Lennart
Bye.
Michael.
--
Michael Hirmke
More information about the systemd-devel
mailing list