Description of problem: systemctl Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
sorry, errant "ENTER" submitted form prematurely. systemctl is not reporting "is-enabled" information for symlinked services. Here, nfs-lock is enabled, but symlinked nfslock service is listed as disabled. This affects our security configuration scripts that look for the historical service name "nfslock". -rw-r--r--. 1 root root 491 Apr 25 11:02 /usr/lib/systemd/system/nfs-lock.service lrwxrwxrwx. 1 root root 16 May 8 19:20 /usr/lib/systemd/system/nfslock.service -> nfs-lock.service # systemctl is-enabled nfs-lock.service && echo y || echo n enabled y # systemctl is-enabled nfslock.service && echo y || echo n disabled n "status" shows the same information: # systemctl status nfslock nfs-lock nfs-lock.service - NFS file locking service. Loaded: loaded (/usr/lib/systemd/system/nfs-lock.service; enabled) Active: active (running) since Thu 2014-05-08 21:27:37 EDT; 3 days ago Main PID: 1036 (rpc.statd) CGroup: /system.slice/nfs-lock.service └─1036 /sbin/rpc.statd May 08 21:27:36 chinacat.cam.nist.gov systemd[1]: Starting NFS file locking service.... May 08 21:27:36 chinacat.cam.nist.gov rpc.statd[1036]: Version 1.3.0 starting May 08 21:27:36 chinacat.cam.nist.gov sm-notify[1037]: Version 1.3.0 starting May 08 21:27:37 chinacat.cam.nist.gov systemd[1]: Started NFS file locking service.. nfs-lock.service - NFS file locking service. Loaded: loaded (/usr/lib/systemd/system/nfs-lock.service; enabled) Active: active (running) since Thu 2014-05-08 21:27:37 EDT; 3 days ago Main PID: 1036 (rpc.statd) CGroup: /system.slice/nfs-lock.service └─1036 /sbin/rpc.statd May 08 21:27:36 chinacat.cam.nist.gov systemd[1]: Starting NFS file locking service.... May 08 21:27:36 chinacat.cam.nist.gov rpc.statd[1036]: Version 1.3.0 starting May 08 21:27:36 chinacat.cam.nist.gov sm-notify[1037]: Version 1.3.0 starting May 08 21:27:37 chinacat.cam.nist.gov systemd[1]: Started NFS file locking service..
systemctl is-enabled is a toold for managing symlinks to (regular) unit files. You are trying to use it to manage symlinks to symlinks to unit files, and that it cannot do for you.
>systemctl is-enabled is a toold for managing symlinks to (regular) unit files. Where is that documented? From the man page, it seems to be just another NAME, similar to status or show commands. 'systemctl disable nfslock' is a silent no-op with a successful exit status. YIKES! 'systemctl enable nfslock' has non-silent "Failed to issue method call: No such file or directory". >You are trying to use it to manage symlinks to symlinks to unit files, and that it cannot do for you. I'm sure it *could* do that if it would read through the additional link. Right now we have inconsistent partial support for service symlinks. Point being: either systemd should support service symlinks or the symlinks should be removed. find /usr/lib/systemd/system -maxdepth 1 -name \*.service -type l /usr/lib/systemd/system/dracut-pre-pivot.service /usr/lib/systemd/system/dbus-org.freedesktop.hostname1.service /usr/lib/systemd/system/dbus-org.freedesktop.machine1.service /usr/lib/systemd/system/nfslock.service /usr/lib/systemd/system/dracut-pre-mount.service /usr/lib/systemd/system/rpcidmapd.service /usr/lib/systemd/system/messagebus.service /usr/lib/systemd/system/dracut-initqueue.service /usr/lib/systemd/system/dracut-mount.service /usr/lib/systemd/system/puppetagent.service /usr/lib/systemd/system/dracut-pre-udev.service /usr/lib/systemd/system/dracut-pre-trigger.service /usr/lib/systemd/system/dracut-cmdline.service /usr/lib/systemd/system/dbus-org.freedesktop.timedate1.service /usr/lib/systemd/system/dbus-org.freedesktop.locale1.service /usr/lib/systemd/system/dbus-org.freedesktop.login1.service /usr/lib/systemd/system/rpcsvcgssd.service /usr/lib/systemd/system/dracut-shutdown.service /usr/lib/systemd/system/rpcgssd.service /usr/lib/systemd/system/nfs.service /usr/lib/systemd/system/autovt@.service
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This bug is basically a subset of #1014311. The upstream patch, AFAIK, fixes the issue with "is-enabled" as well. *** This bug has been marked as a duplicate of bug 1014311 ***