Add triggershell service logs command
CI / Checks (push) Failing after 48s
CI / Publish to npm registry (push) Skipped

Thin wrapper around journalctl, consistent with the existing status/uninstall wrappers around systemctl.
This commit is contained in:
2026-08-19 17:58:41 +02:00
parent 96a66fc857
commit e63129d156
4 changed files with 45 additions and 3 deletions
+3 -3
View File
@@ -74,9 +74,9 @@ installs a per-user unit (`~/.config/systemd/user/triggershell.service`, no root
targets `/etc/systemd/system/` instead and prints the `sudo` commands to run if not already root.
`install` reloads the systemd daemon but does not enable/start the unit itself — that's a separate,
explicit `systemctl --user enable --now triggershell`, since it's the point where the service
actually starts listening and running scripts. `triggershell service status`/`uninstall` are thin
wrappers around `systemctl`; log tailing is just `journalctl --user -u triggershell -f` — not
reimplemented.
actually starts listening and running scripts. `triggershell service status`/`uninstall`/`logs` are
thin wrappers around `systemctl`/`journalctl` respectively - no unit-file parsing or log storage of
our own, journald already does that.
## Cross-module-graph state