diff options
| author | Christian Poessinger <christian@poessinger.com> | 2021-08-13 21:15:58 +0200 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2021-08-13 21:33:09 +0200 |
| commit | 2b8854761c8ed419b2a2f1e02810c3f68f1d72b6 (patch) | |
| tree | 1f9770c136cc5a107fbf1f35f6b671b5481128eb /interface-definitions/include/nat-rule.xml.i | |
| parent | da94e0a736874d9a6420ec1aa754efcec684b390 (diff) | |
| download | vyos-1x-2b8854761c8ed419b2a2f1e02810c3f68f1d72b6.tar.gz vyos-1x-2b8854761c8ed419b2a2f1e02810c3f68f1d72b6.zip | |
vyos.util: "harden" is_systemd_service_running() function
Inspired by the comments of https://unix.stackexchange.com/a/435317 use a more
robust approach. A service can be "active" but not "running" (e.g. restarting
with a configuration error). We can now test if a systemd unit is "activated"
and if it is "running" at all.
>>> from vyos.util import is_systemd_service_active
>>> from vyos.util import is_systemd_service_running
>>> is_systemd_service_active('ssh')
True
>>> is_systemd_service_running('sshd')
False
>>> is_systemd_service_running('ssh')
True
Diffstat (limited to 'interface-definitions/include/nat-rule.xml.i')
0 files changed, 0 insertions, 0 deletions