How do I reload a group of systemd services?
Clash Royale CLAN TAG#URR8PPP
up vote
8
down vote
favorite
I want to reload (not restart!) a group of services upon an event.
For example, if I update my SSL certificates, I want every service that uses them reloaded (nginx and postfix come to mind). Neither I want to remember which services on a given server use SSL certificates. It should be enough to have them grouped when they were configured.
On the other hand, I'd like to avoid changing .service files provided with the packages, because this will require manual intervention during updates.
How do I accomplish that?
There is an option to stop a group of services on request, but this would make them inaccessible for a second or two, or worse - they may stay down until fixed. I can't afford that.
systemd
edited Apr 13 '17 at 12:36
Community♦
1
asked Jan 3 '17 at 9:01
sanmai
492515
add a comment |Â
up vote
8
down vote
favorite
I want to reload (not restart!) a group of services upon an event.
For example, if I update my SSL certificates, I want every service that uses them reloaded (nginx and postfix come to mind). Neither I want to remember which services on a given server use SSL certificates. It should be enough to have them grouped when they were configured.
On the other hand, I'd like to avoid changing .service files provided with the packages, because this will require manual intervention during updates.
How do I accomplish that?
There is an option to stop a group of services on request, but this would make them inaccessible for a second or two, or worse - they may stay down until fixed. I can't afford that.
systemd
edited Apr 13 '17 at 12:36
Community♦
1
asked Jan 3 '17 at 9:01
sanmai
492515
I'm not sure how you deploy certs, but here is also a pre-hook and post-hook for most automagic renewals/opt/letsencrypt/letsencrypt-auto renew --pre-hook "service nginx stop; service postfix stop; service squid stop" --post-hook "service nginx start; service postfix start; service squid start"also: certmonger has postsave and presave commands
– Jacob Evans
Apr 1 '17 at 17:40
@JacobEvans That's what I use! Earlier there was a problem in a config file parser for certbot: it didn't permit semicolons. Therefore you had to use a command line argument, or do it in one go. Right now all this is unnecessarily.
– sanmai
Apr 2 '17 at 10:42
if you make your.servicefile edits as overrides you can avoid the updating problem.sudo systemctl edit foo.servicewill store your changes in/etc/systemd/system/foo.service.d/override.confrather than alter the installedfoo.servicefile.
– quixotic
Apr 2 '17 at 11:59
add a comment |Â
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I want to reload (not restart!) a group of services upon an event.
For example, if I update my SSL certificates, I want every service that uses them reloaded (nginx and postfix come to mind). Neither I want to remember which services on a given server use SSL certificates. It should be enough to have them grouped when they were configured.
On the other hand, I'd like to avoid changing .service files provided with the packages, because this will require manual intervention during updates.
How do I accomplish that?
There is an option to stop a group of services on request, but this would make them inaccessible for a second or two, or worse - they may stay down until fixed. I can't afford that.
systemd
edited Apr 13 '17 at 12:36
Community♦
1
asked Jan 3 '17 at 9:01
sanmai
492515
I want to reload (not restart!) a group of services upon an event.
For example, if I update my SSL certificates, I want every service that uses them reloaded (nginx and postfix come to mind). Neither I want to remember which services on a given server use SSL certificates. It should be enough to have them grouped when they were configured.
On the other hand, I'd like to avoid changing .service files provided with the packages, because this will require manual intervention during updates.
How do I accomplish that?
There is an option to stop a group of services on request, but this would make them inaccessible for a second or two, or worse - they may stay down until fixed. I can't afford that.
systemd
systemd
edited Apr 13 '17 at 12:36
Community♦
1
asked Jan 3 '17 at 9:01
sanmai
492515
edited Apr 13 '17 at 12:36
Community♦
1
asked Jan 3 '17 at 9:01
sanmai
492515
edited Apr 13 '17 at 12:36
Community♦
1
edited Apr 13 '17 at 12:36
Community♦
1
edited Apr 13 '17 at 12:36
Community♦
1
1
asked Jan 3 '17 at 9:01
sanmai
492515
asked Jan 3 '17 at 9:01
sanmai
492515
asked Jan 3 '17 at 9:01
sanmai
492515
492515
I'm not sure how you deploy certs, but here is also a pre-hook and post-hook for most automagic renewals/opt/letsencrypt/letsencrypt-auto renew --pre-hook "service nginx stop; service postfix stop; service squid stop" --post-hook "service nginx start; service postfix start; service squid start"also: certmonger has postsave and presave commands
– Jacob Evans
Apr 1 '17 at 17:40
@JacobEvans That's what I use! Earlier there was a problem in a config file parser for certbot: it didn't permit semicolons. Therefore you had to use a command line argument, or do it in one go. Right now all this is unnecessarily.
– sanmai
Apr 2 '17 at 10:42
if you make your.servicefile edits as overrides you can avoid the updating problem.sudo systemctl edit foo.servicewill store your changes in/etc/systemd/system/foo.service.d/override.confrather than alter the installedfoo.servicefile.
– quixotic
Apr 2 '17 at 11:59
add a comment |Â
I'm not sure how you deploy certs, but here is also a pre-hook and post-hook for most automagic renewals/opt/letsencrypt/letsencrypt-auto renew --pre-hook "service nginx stop; service postfix stop; service squid stop" --post-hook "service nginx start; service postfix start; service squid start"also: certmonger has postsave and presave commands
– Jacob Evans
Apr 1 '17 at 17:40
@JacobEvans That's what I use! Earlier there was a problem in a config file parser for certbot: it didn't permit semicolons. Therefore you had to use a command line argument, or do it in one go. Right now all this is unnecessarily.
– sanmai
Apr 2 '17 at 10:42
if you make your.servicefile edits as overrides you can avoid the updating problem.sudo systemctl edit foo.servicewill store your changes in/etc/systemd/system/foo.service.d/override.confrather than alter the installedfoo.servicefile.
– quixotic
Apr 2 '17 at 11:59
I'm not sure how you deploy certs, but here is also a pre-hook and post-hook for most automagic renewals
/opt/letsencrypt/letsencrypt-auto renew --pre-hook "service nginx stop; service postfix stop; service squid stop" --post-hook "service nginx start; service postfix start; service squid start" also: certmonger has postsave and presave commands– Jacob Evans
Apr 1 '17 at 17:40
I'm not sure how you deploy certs, but here is also a pre-hook and post-hook for most automagic renewals
/opt/letsencrypt/letsencrypt-auto renew --pre-hook "service nginx stop; service postfix stop; service squid stop" --post-hook "service nginx start; service postfix start; service squid start" also: certmonger has postsave and presave commands– Jacob Evans
Apr 1 '17 at 17:40
@JacobEvans That's what I use! Earlier there was a problem in a config file parser for certbot: it didn't permit semicolons. Therefore you had to use a command line argument, or do it in one go. Right now all this is unnecessarily.
– sanmai
Apr 2 '17 at 10:42
@JacobEvans That's what I use! Earlier there was a problem in a config file parser for certbot: it didn't permit semicolons. Therefore you had to use a command line argument, or do it in one go. Right now all this is unnecessarily.
– sanmai
Apr 2 '17 at 10:42
if you make your
.service file edits as overrides you can avoid the updating problem. sudo systemctl edit foo.service will store your changes in /etc/systemd/system/foo.service.d/override.conf rather than alter the installed foo.service file.– quixotic
Apr 2 '17 at 11:59
if you make your
.service file edits as overrides you can avoid the updating problem. sudo systemctl edit foo.service will store your changes in /etc/systemd/system/foo.service.d/override.conf rather than alter the installed foo.service file.– quixotic
Apr 2 '17 at 11:59
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
16
down vote
accepted
Create /etc/systemd/system/ssl-reload.target with the following contents.
[Unit]
Description=Services which need reloaded with SSL certs are updated.
PropagatesReloadTo=nginx postfix
Then create another file: /etc/systemd/system/ssl-reload.path
[Unit]
Description=Restart services which use SSL when the cert directory changes
[Path]
PathChanged=/path/to/your/ssl/certs/dir
[Install]
WantedBy=multi-user.target
Then:
systemctl enable ssl-reload.path
systemctl start ssl-reload.path
With that said, after changing something in your SSL directory, the desired services should be reloaded automatically.
if you don't want the automatic behavior, then don't use the .path file, and just issue systemctl reload ssl-reload.target manually after you change SSL files.
edited Sep 27 at 17:14
Unda
1034
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
16
down vote
accepted
Create /etc/systemd/system/ssl-reload.target with the following contents.
[Unit]
Description=Services which need reloaded with SSL certs are updated.
PropagatesReloadTo=nginx postfix
Then create another file: /etc/systemd/system/ssl-reload.path
[Unit]
Description=Restart services which use SSL when the cert directory changes
[Path]
PathChanged=/path/to/your/ssl/certs/dir
[Install]
WantedBy=multi-user.target
Then:
systemctl enable ssl-reload.path
systemctl start ssl-reload.path
With that said, after changing something in your SSL directory, the desired services should be reloaded automatically.
if you don't want the automatic behavior, then don't use the .path file, and just issue systemctl reload ssl-reload.target manually after you change SSL files.
edited Sep 27 at 17:14
Unda
1034
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
add a comment |Â
up vote
16
down vote
accepted
Create /etc/systemd/system/ssl-reload.target with the following contents.
[Unit]
Description=Services which need reloaded with SSL certs are updated.
PropagatesReloadTo=nginx postfix
Then create another file: /etc/systemd/system/ssl-reload.path
[Unit]
Description=Restart services which use SSL when the cert directory changes
[Path]
PathChanged=/path/to/your/ssl/certs/dir
[Install]
WantedBy=multi-user.target
Then:
systemctl enable ssl-reload.path
systemctl start ssl-reload.path
With that said, after changing something in your SSL directory, the desired services should be reloaded automatically.
if you don't want the automatic behavior, then don't use the .path file, and just issue systemctl reload ssl-reload.target manually after you change SSL files.
edited Sep 27 at 17:14
Unda
1034
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
add a comment |Â
up vote
16
down vote
accepted
up vote
16
down vote
accepted
Create /etc/systemd/system/ssl-reload.target with the following contents.
[Unit]
Description=Services which need reloaded with SSL certs are updated.
PropagatesReloadTo=nginx postfix
Then create another file: /etc/systemd/system/ssl-reload.path
[Unit]
Description=Restart services which use SSL when the cert directory changes
[Path]
PathChanged=/path/to/your/ssl/certs/dir
[Install]
WantedBy=multi-user.target
Then:
systemctl enable ssl-reload.path
systemctl start ssl-reload.path
With that said, after changing something in your SSL directory, the desired services should be reloaded automatically.
if you don't want the automatic behavior, then don't use the .path file, and just issue systemctl reload ssl-reload.target manually after you change SSL files.
edited Sep 27 at 17:14
Unda
1034
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
Create /etc/systemd/system/ssl-reload.target with the following contents.
[Unit]
Description=Services which need reloaded with SSL certs are updated.
PropagatesReloadTo=nginx postfix
Then create another file: /etc/systemd/system/ssl-reload.path
[Unit]
Description=Restart services which use SSL when the cert directory changes
[Path]
PathChanged=/path/to/your/ssl/certs/dir
[Install]
WantedBy=multi-user.target
Then:
systemctl enable ssl-reload.path
systemctl start ssl-reload.path
With that said, after changing something in your SSL directory, the desired services should be reloaded automatically.
if you don't want the automatic behavior, then don't use the .path file, and just issue systemctl reload ssl-reload.target manually after you change SSL files.
edited Sep 27 at 17:14
Unda
1034
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
edited Sep 27 at 17:14
Unda
1034
edited Sep 27 at 17:14
Unda
1034
edited Sep 27 at 17:14
Unda
1034
1034
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
answered Jan 3 '17 at 21:12
Mark Stosberg
3,6561023
3,6561023
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f334471%2fhow-do-i-reload-a-group-of-systemd-services%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I'm not sure how you deploy certs, but here is also a pre-hook and post-hook for most automagic renewals
/opt/letsencrypt/letsencrypt-auto renew --pre-hook "service nginx stop; service postfix stop; service squid stop" --post-hook "service nginx start; service postfix start; service squid start"also: certmonger has postsave and presave commands– Jacob Evans
Apr 1 '17 at 17:40
@JacobEvans That's what I use! Earlier there was a problem in a config file parser for certbot: it didn't permit semicolons. Therefore you had to use a command line argument, or do it in one go. Right now all this is unnecessarily.
– sanmai
Apr 2 '17 at 10:42
if you make your
.servicefile edits as overrides you can avoid the updating problem.sudo systemctl edit foo.servicewill store your changes in/etc/systemd/system/foo.service.d/override.confrather than alter the installedfoo.servicefile.– quixotic
Apr 2 '17 at 11:59