For people from Google: Validate with sudo systemd-analyze verify NAME.service When using a symlink, make sure it uses absolute path Make sure the name is like /etc/systemd/system/*.service Do sudo systemctl daemon-reload after changes
After some research I found that you can’t delete logs for a specific systemd unit, because the logs are interlaced and if you delete only one unit you’ll corrupt the logs, so journalctl doesn’t let you.
By default, a SIGTERM is sent, followed by 90 seconds of waiting followed by a SIGKILL. Killing processes with systemd is very customizable and well-documented. I recommend reading all of man systemd.kill as well as reading about ExecStop= in man systemd.service. To respond to those signals, refer to the signal handling documentation for the language … Read more
The Type=oneshot service unit: blocks on a start operation until the first process exits, and its state will be reported as “activating”; once the first process exits, transitions from “activating” straight to “inactive”, unless RemainAfterExit=true is set (in which case it becomes “active” with no processes!); may have any number (0 or more) of ExecStart= … Read more
By default, a SIGTERM is sent, followed by 90 seconds of waiting followed by a SIGKILL. Killing processes with systemd is very customizable and well-documented. I recommend reading all of man systemd.kill as well as reading about ExecStop= in man systemd.service. To respond to those signals, refer to the signal handling documentation for the language … Read more
The following output options display priority (and facility), but in a different format: journalctl -o verbose journalctl -o json (and json-pretty) journalctl -o export
Maybe stating the obvious reduces the learning effect, but all I did to get the full list of reverse dependencies for shutdown-target as asked in the original post, was: systemctl list-dependencies –after shutdown.target OT: I ran in a problem where the shutdown of a kubernetes system hangs (the machine becomes irresponsive and will not shut … Read more
The comment from Bigon is correct. I was looking in /var/log/syslog, but this is written by rsyslog.service, which systemd stops pretty early in the shutdown process (as indicated by “Stopped System Logging Service” below). After I enabled persistent journald logging instead (Storage=persistent in /etc/systemd/journald.conf and systemctl restart systemd-journald), journalctl -b-1 -u shutdowntest.service shows that my … Read more
Every unit in systemd has a job slot internally, and there can be only one job installed for the unit at a time. Jobs encapsulate state change requests for units in general, but their effects vary according to the unit type. In services, they may initiate a state change request, but the action may run … Read more
You can run the sleep command before your ExecStart with ExecStartPre : [Service] ExecStartPre=/bin/sleep 30