From b1be771aeb85b888df67f3ee4feeb190028e55f8 Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Tue, 4 Jul 2023 15:33:59 +0200
Subject: [PATCH] autopushed

---
 airing of grievances.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/airing of grievances.md b/airing of grievances.md
index 9550b714b..72153c020 100644
--- a/airing of grievances.md	
+++ b/airing of grievances.md	
@@ -19,5 +19,5 @@ I love Systemd; I remember curating SysV Init scripts and I think the process of
 
 Why is it so hard to just make sure a service will actually start and keep retrying forever if it can't start? There are several incantations in the configuration spec that *seem* like they should achieve indefinite retries, but really don't (or do only in some cases). I understand why you'd want to have something like a sane retry policy (with backoff), but I really would like to tell it: just keep trying for me. Under no situation it seems reasonable for me to find a service marked as `inactive (dead)`, run start on it and have it work flawlessly. The computer should have done that for me.
 
-Also, why is it non-trivial to go from operating over a service (with e.g. `systemctl --user status/stop/start`) to operating over its logs? For the latter you need (checks notes) [[journalctl]] …
+Also, why is it non-trivial to go from operating over a service (with e.g. `systemctl --user status/stop/start foo`) to operating over its logs? For the latter you need (checks notes) `[[journalctl]] --user-unit foo`. Maybe it just took me longer than normal to find this, but it's unclear to me why `systemctl --user logs` doesn't exist, or why it's --user-unit in the case of journalctl instead of --user.