Systemd Declaring a Service Dependency: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
==Create a httpd systemd service configuration directory== | ==Create a httpd systemd service configuration directory== | ||
< | <font size=-2> | ||
/etc/systemd/system/httpd.service.d | /etc/systemd/system/httpd.service.d | ||
</ | </font> | ||
==Create a httpd systemd service configuration file that expresses the dependency== | ==Create a httpd systemd service configuration file that expresses the dependency== |
Revision as of 02:41, 1 January 2024
Internal
Overview
This example shows how to declare a dependency between httpd and network services - the system should not attempt to start httpd unless the network service are started, otherwise httpd won't find the network interfaces to bind to. For more details on concepts behind dependencies, see:
Procedure
Create a httpd systemd service configuration directory
/etc/systemd/system/httpd.service.d
Create a httpd systemd service configuration file that expresses the dependency
Create a /etc/systemd/system/httpd.service.d/http-extra.conf file with the following content:
[Unit]
Requires=network-online.target
After=network-online.target
For more details on the structure of a systemd unit file, see the [Unit] section of a unit file.
Procedure 2
TODO: Document this, it worked expressing the haproxy dependency on named.
Declare the dependency directly on a service, in the dependent service unit file:
... Requires=named.service After=named.service ...
This also worked:
... After=network-online.target sshd-keygen.service Wants=sshd-keygen.service ...