Bug#732122: semantics of boolean event specification not defined in init(5)

2013-12-20 Thread James Hunt
Hi Ian, I've expanded the section on 'start on' in upstream commit r1584: http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/revision/1584 Kind regards, James. -- James Hunt #upstart on freenode http://upstart.ubuntu.com/cookbook https://lists.ubuntu.c

Bug#732122: semantics of boolean event specification not defined in init(5)

2013-12-17 Thread Nikolaus Rath
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

Bug#732122: semantics of boolean event specification not defined in init(5)

2013-12-14 Thread Ian Jackson
Package: upstart Version: 1.20-1 Severity: minor The documentation says that a job can be started on a boolean combination of events. Of course a boolean combination of events is semantically meaningless, unless events are thought to occur simultaneously (which I'm pretty sure they don't, in upst