[systemd-bugs] [Bug 69575] New: systemd emits UnitNew in response to Properties.Get, potentially leading to loops.

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 69575
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: systemd emits UnitNew in response to Properties.Get,
                    potentially leading to loops.
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: marius.vollmer at redhat.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Systemd 207, with patches.

I have a program that reacts to UnitNew signals from systemd by issuing a
Properties.GetAll call to the new unit.

Now, if someone anywhere issues a Properties.GetAll call (or probably any other
call) for a non-loaded unit, systemd will emit two UnitNew/UnitRemoved signals
back to back.

By the time my program has received the UnitNew signal of the pair and issued
the Properties.GetAll call, the unit has already disapeared again from systemds
memory, and the Properties.GetAll call results in another pair of
UnitNew/UnitRemove signals.

This will then cause my program to call Properties.GetAll again, leading to a
tight infinite loop.

This didn't happen with systemd 201.

I think it is reasonable to react to a UnitNew signal with a Properties.GetAll
call.  No?

-- 
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/20130919/58fcac04/attachment.html>