Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.18.x] Do not systemctl enable individual services #1334

Merged
merged 1 commit into from
Nov 8, 2023

Conversation

vpodzime
Copy link
Contributor

@vpodzime vpodzime commented Nov 8, 2023

The cfengine3.service uses Wants to start all the other available CFEngine services. systemctl enable on one of the individual services causes them to be started in their respective .target (e.g. multi-user.target) and thus systemctl disable cfengine3 is not enough to stop them from being started on boot.

Being able to enable individual services is useful, but it shouldn't be done by default.

(cherry picked from commit f53a8f1)

The `cfengine3.service` uses `Wants` to start all the other
available CFEngine services. `systemctl enable` on one of the
individual services causes them to be started in their respective
`.target` (e.g. `multi-user.target`) and thus `systemctl disable
cfengine3` is not enough to stop them from being started on boot.

Being able to enable individual services is useful, but it
shouldn't be done by default.

(cherry picked from commit f53a8f1)
@vpodzime vpodzime merged commit 163e735 into cfengine:3.18.x Nov 8, 2023
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants