You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added service states "active" and "inactive" for systemd
This change brings understanding of "active" and "inactive" states for services
when managed by systemd. An "active" service state means the service should be
running. An "inactive" service state means the service should not be running.
NOTE: When "active" or "inactive" service states are used, no promises about a
services state on boot are made.
Ticket: ENT-6074
Changelog: Title
# @brief Standard services bundle, used by CFEngine by default
83
83
# @author CFEngine AS
84
84
# @param service Name of service to control
85
-
# @param state The desired state for that service: "start", "restart", "reload", "stop", or "disable". "enable", "enabled", and "disabled" are also able to be used when systemd is detected.
85
+
# @param state The desired state for that service: "start", "restart", "reload", "stop", or "disable". "enable", "enabled", and "disabled" are also able to be used when systemd is detected. "active" and "inactive" states are supported for systemd managed hosts and can be used for controlling the services currently running state, but make no promises about the service state on boot.
86
86
#
87
87
# This bundle is used by CFEngine if you don't specify a services
88
88
# handler explicitly, and will work with systemd or chkconfig or other
0 commit comments