As far as I know, specifying a boolean combination of events "forces" them to occur simultaneously by "latching" all involved events.
In other words, if you have a job depending on "A and B", and a program foo then emits event A, then foo (by default) going to block until some other program emits "B". This can be worked around by explicitly specifying that an event should be emitted non-blocking. Of course, if the program that will emit B is itself waiting for foo to start, you get a deadlocked system. This is essentially what I'm complaining about in https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/964207 Best, Nikolaus -- Encrypted emails preferred. PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
