[systemd-bugs] [Bug 86520] New: Race condition on systemd-run --scope

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 86520
           Summary: Race condition on systemd-run --scope
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: critical
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: umut at tezduyar.com
        QA Contact: systemd-bugs at lists.freedesktop.org

Follow up on thread:
http://lists.freedesktop.org/archives/systemd-devel/2014-October/024482.html

I have stumbled on a race condition on systemd-run --scope command. Due to race
condition, unit might show up as active/running even though there is no process
in the cgroup.

The impact is big for us. We are starting some legacy scripts as scopes and a
script might have something like this in the beginning.

systemd-run --unit hello --scope /myscript

#!/bins/h

. /etc/configuration

if [ $ENABLED == 'no' ]
    return

Later on, when the script is enabled with ENABLED=yes, running systemd-run
--unit hello --scope /myscript is returning immediately since systemd is
considering hello.scope already active.

-- 
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/20141121/7b0f8d55/attachment.html>