[systemd-bugs] [Bug 88746] New: Masked unit might still be dbus activated due to systemd not understanding dbus symbolic link

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=88746

            Bug ID: 88746
           Summary: Masked unit might still be dbus activated due to
                    systemd not understanding dbus symbolic link
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: umut at tezduyar.com
        QA Contact: systemd-bugs at lists.freedesktop.org

This is on systemd 216

I have 2 services and both have very similar structure. The only difference
between them is one of them is wanted by multi-user.target and other one is not
started at all. 

If I mask both services, service that is wanted by multi-user.target cannot be
dbus activated (expected) and other service can be dbus activated even though
the service is masked. 

The reason why systemd is confused is, systemd doesn't pick up the symbolic
link of dbus to the original service file. 

# recording-fixer is missing the additional name
dbus-com.axis.RecordingFixer.service
[root at axis-00408cecff49 /etc/systemd/system]2934# systemctl show
recording-fixer | grep Names
Names=recording-fixer.service

[root at axis-00408cecff49 /etc/systemd/system]2934# systemctl show
storage-manager | grep Names
Names=storage-manager.service dbus-com.axis.Storage.service

[root at axis-00408cecff49 /usr/lib/systemd/system]2737# ls -al
recording-fixer.service storage-manager.service 
-rw-r--r--    1 root     root           216 Nov 24  2014
recording-fixer.service
-rw-r--r--    1 root     root           213 Dec 12  2014
storage-manager.service

[root at axis-00408cecff49 /usr/lib/systemd/system]2737# ls -al
dbus-com.axis.RecordingFixer.service dbus-com.axis.Storage.service 
lrwxrwxrwx    1 root     root            23 Jan 21  2015
dbus-com.axis.RecordingFixer.service -> recording-fixer.service
lrwxrwxrwx    1 root     root            23 Jan 21  2015
dbus-com.axis.Storage.service -> storage-manager.service

[root at axis-00408cecff49 /usr/lib/systemd/system]2737# systemctl status
storage-manager
● storage-manager.service
   Loaded: masked (/dev/null)
   Active: inactive (dead) since Thu 2007-02-01 02:24:36 GMT; 1min 20s ago
 Main PID: 1292 (code=exited, status=0/SUCCESS)

[root at axis-00408cecff49 /usr/lib/systemd/system]2737# systemctl status
dbus-com.axis.Storage.service
● storage-manager.service
   Loaded: masked (/dev/null)
   Active: inactive (dead) since Thu 2007-02-01 02:24:36 GMT; 1min 29s ago
 Main PID: 1292 (code=exited, status=0/SUCCESS)

[root at axis-00408cecff49 /usr/lib/systemd/system]2737# systemctl status
recording-fixer.service 
● recording-fixer.service
   Loaded: masked (/dev/null)
   Active: inactive (dead)

[root at axis-00408cecff49 /usr/lib/systemd/system]2737# systemctl status
dbus-com.axis.RecordingFixer.service
● recording-fixer.service - Fix broken recording
   Loaded: loaded (/usr/lib/systemd/system/recording-fixer.service; masked)
   Active: inactive (dead)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150123/57e437e9/attachment.html>