[systemd-bugs] [Bug 69989] New: StopWhenUnneeded=yes does not stop service even though there's nothing depending on it

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 69989
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: StopWhenUnneeded=yes does not stop service even though
                    there's nothing depending on it
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: brunocodutra at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I have a very simple mount file like follows

[Unit]
BindsTo=dev-disk-by\<DEVICE DESCRIPTOR>.device
Conflicts=umount.target
Before=umount.target
After=dev-disk-by\<DEVICE DESCRIPTOR>.device
StopWhenUnneeded=true

[Mount]
What=/dev/disk/by-uuid/<DEVICE UUID>
Where=/mount/point
Type=ext4

I also have a service which BindsTo and is set to be executed After the
previous mount file. 

When this service is started, after plugging the device in and having udev
detect it, the mount file is started as expected and the mount point
successfully established. The service executes a simple task and finishes
successfully. The mount file is expected to be sopped given StopWhenUnneeded is
set to true, but that does not occur and the mount point is left mounted until
manual intervention.

In a previous version, which I sadly cannot precise, this setup used to behave
as expected.

-- 
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/20131001/9e9a2736/attachment.html>