mirror of
https://github.com/systemd/systemd.git
synced 2024-12-23 21:35:11 +03:00
docs: PrepareForSuspend() is not a valid signal name
This commit is contained in:
parent
3f1c304803
commit
7248912d10
@ -101,7 +101,7 @@ The signal with _False_ is usually the signal on which applications request a ne
|
|||||||
|
|
||||||
Note that watching PrepareForShutdown(true)/PrepareForSleep(true) without taking a delay lock is racy and should not be done, as any code that an application might want to execute on this signal might not actually finish before the suspend/shutdown cycle is executed.
|
Note that watching PrepareForShutdown(true)/PrepareForSleep(true) without taking a delay lock is racy and should not be done, as any code that an application might want to execute on this signal might not actually finish before the suspend/shutdown cycle is executed.
|
||||||
|
|
||||||
_Again_: if you watch PrepareForSuspend(true), then you really should have taken a delay lock first. PrepareForShutdown(false) may be subscribed to by applications which want to be notified about system resume events.
|
_Again_: if you watch PrepareForShutdown(true)/PrepareForSleep(true), then you really should have taken a delay lock first. PrepareForSleep(false) may be subscribed to by applications which want to be notified about system resume events.
|
||||||
|
|
||||||
Note that this will only be sent out for suspend/resume cycles done via logind, i.e. generally only for high-level user-induced suspend cycles, and not automatic, low-level kernel induced ones which might exist on certain devices with more aggressive power management.
|
Note that this will only be sent out for suspend/resume cycles done via logind, i.e. generally only for high-level user-induced suspend cycles, and not automatic, low-level kernel induced ones which might exist on certain devices with more aggressive power management.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user