<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Masked unit might still be dbus activated due to systemd not understanding dbus symbolic link"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88746">88746</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Masked unit might still be dbus activated due to systemd not understanding dbus symbolic link
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>umut@tezduyar.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>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@axis-00408cecff49 /etc/systemd/system]2934# systemctl show
recording-fixer | grep Names
Names=recording-fixer.service
[root@axis-00408cecff49 /etc/systemd/system]2934# systemctl show
storage-manager | grep Names
Names=storage-manager.service dbus-com.axis.Storage.service
[root@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@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@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@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@axis-00408cecff49 /usr/lib/systemd/system]2737# systemctl status
recording-fixer.service
● recording-fixer.service
Loaded: masked (/dev/null)
Active: inactive (dead)
[root@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)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>