diff options
author | Jake Hunsaker <jhunsake@redhat.com> | 2022-06-10 12:23:39 -0400 |
---|---|---|
committer | Jake Hunsaker <jhunsake@redhat.com> | 2022-06-15 11:37:45 -0400 |
commit | c55d6b8fb0d90fba4182f7cdf6d753652f119fd9 (patch) | |
tree | 3a9e5799fcea84b61a850da6670efd7f2e221366 /man | |
parent | cbdd83b7ef984768aaf3a9a2c661b28d32f01aa2 (diff) | |
download | sos-c55d6b8fb0d90fba4182f7cdf6d753652f119fd9.tar.gz |
[InitSystem] Allow toggle of default `is_running` result
The base `InitSystem` used when systemd is not present (or at least
functional), defaults to returning `True` for all probes, in an effort
to not inadvertantly block service queries.
This works well for most scenarios, however it backfires when checking
for runlevel-analogous systemd targets for items such as the `cantboot`
preset - in that the base `InitSystem` will always enable that preset.
Fix that by allowing calls to `InitSystem.is_running()` to specify a
default value to return, instead of blindly always returning `True`.
Similarly, update the preset check to default to `False` to avoid
improperly enabling that preset when systemd is unavailable.
Closes: #2913
Signed-off-by: Jake Hunsaker <jhunsake@redhat.com>
Diffstat (limited to 'man')
0 files changed, 0 insertions, 0 deletions