From 7248912d106ec2a6b63042453e072bcf326120dd Mon Sep 17 00:00:00 2001 From: Frantisek Sumsal Date: Fri, 26 Apr 2024 14:27:03 +0200 Subject: [PATCH] docs: PrepareForSuspend() is not a valid signal name --- docs/INHIBITOR_LOCKS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/INHIBITOR_LOCKS.md b/docs/INHIBITOR_LOCKS.md index f11762e7b85..7b98d4bac08 100644 --- a/docs/INHIBITOR_LOCKS.md +++ b/docs/INHIBITOR_LOCKS.md @@ -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. -_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.