Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
Jon Severinsson [2015-04-13 15:18 +0200]: > Debian patches the systemd legacy sysv support to use update-rc.d (the Debian- > native equivalent) instead of chkconfig, but update-rc.d does not have a is- > enabled feature, so is-enabled will not work on legacy init scripts in the > Debian build of systemd... For the record, this is tracked in https://bugs.debian.org/705254 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
On Sun, 12.04.15 21:00, Nusenu (nus...@openmailbox.org) wrote: > 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? On Fedora, when systemctl encounters a sysv service it dispatches this to chkconfig. I offered to merge similar code that dispatches this to update-rc.d on Debian-derived distros, but so far I didn't get a good patch for this from the Debian guys. Offer is still valid though... Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
måndagen den 13 april 2015 07:26:14 skrev Nusenu: > Hi Andrei, > > thanks for your reply. > > > systemctl should still support it if your system supports chkconfig > > to manage initscripts. > > chkconfig was indeed not installed, but even after installing it, the > > is-enabled command output and return codes do not change: > >> Output in such cases: > >> > >> "Failed to get unit file state for FOO.service: No such file or director > >> y" > > Is this considered a bug? > > thanks, > Nusenu > > testing on: > Debian 8 (chkconfig installed) with systemd 215-14 and > Ubuntu 15.04 with systemd 219-7ubuntu1 (no chkconfig available) Debian patches the systemd legacy sysv support to use update-rc.d (the Debian- native equivalent) instead of chkconfig, but update-rc.d does not have a is- enabled feature, so is-enabled will not work on legacy init scripts in the Debian build of systemd... ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
> thanks for your reply. > >> systemctl should still support it if your system supports >> chkconfig to manage initscripts. > > chkconfig was indeed not installed, but even after installing it, > the is-enabled command output and return codes do not change: > >>> Output in such cases: >> >>> "Failed to get unit file state for FOO.service: No such file or >>> director y" > > Is this considered a bug? since it works on RHEL 7 with systemd 208 I'll file this bug against debian. systemctl is-enabled tor tor.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig tor --level=5 enabled ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
Hi Andrei, thanks for your reply. > systemctl should still support it if your system supports chkconfig > to manage initscripts. chkconfig was indeed not installed, but even after installing it, the is-enabled command output and return codes do not change: >> Output in such cases: > >> "Failed to get unit file state for FOO.service: No such file or director >> y" Is this considered a bug? thanks, Nusenu testing on: Debian 8 (chkconfig installed) with systemd 215-14 and Ubuntu 15.04 with systemd 219-7ubuntu1 (no chkconfig available) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Sun, 12 Apr 2015 21:00:38 + Nusenu пишет: > -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- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?
-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? 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. thanks, Nusenu -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVKtz2AAoJEFv7XvVCELh0VhIP/RaV7gf779K4dzWUYJHA29ks d14KxPa7JPgn9RKfbq+wi1ZE84v+l5g6Gy5lR+3dMwJC8lj2mJxSlRYyynhIpCnf dHpwMAdAMZxgXpRgLBew0wLLbYpV+UjSLwXndqdf0ZJynwyIJAWQvwREo7CZrDXy LKEz1L7iAgSpjLvGyzrTabmZuTHIAlMGns1Q4UMJbMRhgm/wgxpFnKfZERDo5s6b hql4FydFoIQea9b+yIjh3Gid8ymk+SLprPrEtJZeIIlb0yJUj4f5WDfkopGtvqCR Pl1N0q8Lu8bhqHMpczF3MHrpSlm2Hzap89I7dVHFxxiyz2fYqZeJLLRQEoqcKDXO q328JSj1EbL/BZU6qlDf8ykMG4cB/y8t4lE2kvtLO2WsKUhX1zWSkEIPwVwlc0QI WNawRXGoUY2uLT1NuwbQw4LKnABQMWXi+2TOYfgvl/heeRiVUle9/23pWcjofxNk AlUc+CJFEQnc2cmrZdXU/echZPM3V90Uq/ramgUsmI1KiQqMTLoi1wJ9/neiU/hT ZQexWyejCD1vqwTzUVhkUpLg/90ig2C/KbvNpzwRHWSSTVMy62agbOQth6ar99Y8 tUIUHWwXH9txHlEPBGovs951FgDlMbeG6IGseM1j+K14bMMdjmCtNGa7X6JGcDVJ geJYr+PjlhFsIhjOVu1M =jxrl -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
