[systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?

Andrei Borzenkov arvidjaar at gmail.com
Sun Apr 12 21:51:23 PDT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

В Sun, 12 Apr 2015 21:00:38 +0000
Nusenu <nusenu at openmailbox.org> пишет:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi,
> 
> I'm trying to find out whether I'm looking at an ansible or systemctl
> bug.
> 
> Does systemctl aim to support the 'is-enabled' command for legacy sysv
> initscripts?
> 

systemctl should still support it if your system supports chkconfig
to manage initscripts. 

> Output in such cases:
> 
> "Failed to get unit file state for FOO.service: No such file or director
> y"
> 
> 
> Context: ansible uses 'is-enabled' to find out about the current state
> of a service. In such cases it always believes the service is disabled
> already due to systemctl's return code.
> 
> I had a short look at:
> http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/
> but I didn't find an answer to my question.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlUrS0wACgkQR6LMutpd94yxWwCgmcbREiJ8u29HMzSe3tPQzQMc
jXoAnR+Rimc17TPzd22Jb9jrJ+ImXrah
=xeWl
-----END PGP SIGNATURE-----


More information about the systemd-devel mailing list