flancian/garden
0
0
Fork 0
mirror of https://github.com/flancian/garden.git synced 2026-08-05 22:16:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

autopushed

Browse Source
This commit is contained in:
Flancian
2023-07-04 15:33:59 +02:00
parent 0b3fa6e183
commit b1be771aeb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
airing of grievances.md
+1 -1
View File
@@ -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.