Post History
Assuming that systemctl start $SERVICE.service returns right away (some [poorly] written StartExec commands do not), you can run this: systemctl start $SERVICE.service & journalctl -f -u $SERV...
Answer
#2: Post edited
by
AdminBee
·
2023-08-21T13:37:02Z (over 1 year ago)
Fix (probably) intended formatting
Assuming that `systemctl start $SERVICE.service` returns right away (some [poorly] written StartExec commands do not), you can run this:systemctl start $SERVICE.service & journalctl -f -u $SERVICE.serviceThis is the command I run quite often when needing to investigate the startup logs.
- Assuming that `systemctl start $SERVICE.service` returns right away (some [poorly] written `StartExec` commands do not), you can run this:
- ```
- systemctl start $SERVICE.service & journalctl -f -u $SERVICE.service
- ```
- This is the command I run quite often when needing to investigate the startup logs.
#1: Initial revision
by
bgstack15
·
2023-08-20T19:18:26Z (over 1 year ago)
Assuming that `systemctl start $SERVICE.service` returns right away (some [poorly] written StartExec commands do not), you can run this: systemctl start $SERVICE.service & journalctl -f -u $SERVICE.service This is the command I run quite often when needing to investigate the startup logs.