From 621def9bc40ee61b6eef377eb483f6cab07779bb Mon Sep 17 00:00:00 2001
From: Maximilian Seidler <78690852+PaideiaDilemma@users.noreply.github.com>
Date: Wed, 13 Mar 2024 22:26:07 +0100
Subject: [PATCH] hyprlock: mention SIGUSR signals (#528)

---
 pages/Hypr Ecosystem/hyprlock.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/pages/Hypr Ecosystem/hyprlock.md b/pages/Hypr Ecosystem/hyprlock.md
index 4bfe415..5dc148e 100644
--- a/pages/Hypr Ecosystem/hyprlock.md	
+++ b/pages/Hypr Ecosystem/hyprlock.md	
@@ -151,4 +151,7 @@ Worth noting:
  - `$ATTEMPTS[<string>]` format can be used to show `<string>` when there are no failed attempts. You can use pango-markup here. `<string>` can be empty to hide.
  - **do not** run commands that never exit. This will hang the AsyncResourceGatherer and you won't have a good time.
 
+## User Signals
 
+- `SIGUSR1` - unlocks hyprlock. For example, you can switch to a another tty and run `pkill -USR1 hyprlock`.
+- `SIGUSR2` - updates labels. See above.