Skip to content

Commit

Permalink
Systemd-start: clarify exit command variants (#868)
Browse files Browse the repository at this point in the history
Resort to `terminate-users` only in case of problems.
  • Loading branch information
Vladimir-csp authored Nov 14, 2024
1 parent fa8dd7d commit 052b616
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions pages/Configuring/Dispatchers.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ layout pages (See the sidebar).

{{< callout type=warning >}}

[uwsm](../../Useful-Utilities/Systemd-start) users should avoid using `exit` dispatcher, or terminating Hyprland process directly, as exiting Hyprland this way removes it from under its clients and may cause some systemd services to enter inconsistent states causing problems in the next session. Use `exec, loginctl terminate-user ""` instead.
[uwsm](../../Useful-Utilities/Systemd-start) users should avoid using `exit` dispatcher, or terminating Hyprland process directly, as exiting Hyprland this way removes it from under its clients and interferes with ordered shutdown sequence. Use `exec, uwsm stop` (or [other variants](https://github.com/Vladimir-csp/uwsm#how-to-stop)) which will gracefully bring down graphical session (and login session bound to it, if any). If you experience problems with units entering inconsistent states, affecting subsequent sessions, use `exec, loginctl terminate-user ""` instead (terminates all units of the user).

It's also strongly advised to replace the `exit` dispatcher with `exec, loginctl terminate-user ""` inside `hyprland.conf` keybinds section.
It's also strongly advised to replace the `exit` dispatcher inside `hyprland.conf` keybinds section accordingly.

{{< /callout >}}

Expand Down

0 comments on commit 052b616

Please sign in to comment.