Difference between revisions of "Systemd"
From Leaky
(systemd tips) |
(→Assorted commands) |
||
Line 32: | Line 32: | ||
systemctl reenable unitname | systemctl reenable unitname | ||
+ | |||
+ | Things like nagios-nrpe on a multi-homed server where it's bound to just one interface might fail to start automatically because it tries to bind to the interface before it's been brought up. The solution is to make it wait for the network to be fully started. | ||
+ | |||
+ | systemctl edit --full nrpe.service | ||
+ | |||
+ | Replace the line | ||
+ | |||
+ | Requires=network.target | ||
+ | |||
+ | with the following | ||
+ | |||
+ | Requires=network.target network-online.target | ||
+ | Wants=network-online.target | ||
+ | After=network.target network-online.target |
Latest revision as of 08:56, 19 January 2018
Project page: https://freedesktop.org/wiki/Software/systemd/
Page with some useful info: https://wiki.archlinux.org/index.php/Systemd
Assorted commands
Reload all units
systemctl daemon-reload
Equivalent of
chkconfig unitname on
is
systemctl enable unitname
Equivalent of
service unitname start
is
systemctl start unitname
If you've created a file in /etc/systemd/system/ and you need to edit it, you can use
systemctl edit --full unitname
This will open the file in your editor and reload it afterwards. If you've edited the file directly, simply reload it afterwards with
systemctl reenable unitname
Things like nagios-nrpe on a multi-homed server where it's bound to just one interface might fail to start automatically because it tries to bind to the interface before it's been brought up. The solution is to make it wait for the network to be fully started.
systemctl edit --full nrpe.service
Replace the line
Requires=network.target
with the following
Requires=network.target network-online.target Wants=network-online.target After=network.target network-online.target