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

Back-port #31677 to 2016.3 #35244

Merged
merged 1 commit into from
Aug 6, 2016
Merged

Back-port #31677 to 2016.3 #35244

merged 1 commit into from
Aug 6, 2016

Conversation

rallytime
Copy link
Contributor

Back-port #31677 to 2016.3

…t in SysV

This fixes situations, when a server switched from SysV to Systemd.
SysV symlinks are still in place and Salt incorrectly determines, that
service is already enabled.

For example:
~$ salt-call --local service.enabled spamassassin
[INFO    ] Executing command 'systemctl is-enabled spamassassin.service'
[INFO    ] Executing command 'runlevel' in directory '/root'
local:
    True

However:

~$ systemctl is-enabled spamassassin.service
disabled

~$ find /etc/rc*.d/ -name
'*spamassassin'
/etc/rc0.d/K02spamassassin
/etc/rc1.d/K02spamassassin
/etc/rc2.d/S02spamassassin
/etc/rc3.d/S02spamassassin
/etc/rc4.d/S02spamassassin
/etc/rc5.d/S02spamassassin
/etc/rc6.d/K02spamassassin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants