misleading "idiom" example in Section 11.29.1.1 ?

[dampier]

Bullet #5 in that section currently reads :

     If you want your job to start when all network devices are active, specify:

          start on stopped networking

     Note that as of Ubuntu Oneiric, you could also say:

          start on static-network-up

I was using the first form in an upstart script on Ubuntu Quantal today, and it seemed this condition did exactly the opposite!

That is, the script activated when the host was shutting down (stopping "networking" job?), not when the host was starting up (having "stopped" the hypothetical "networking [setup]" job this example had me imagining). Has the meaning of the "networking" job changed over time?

Of course, switching to the second form did exactly as I'd intended.

I hope you'll forgive my n00b ignorance if I'm missing something obvious here. I'd like to thank the maintainers for this powerful system facility, and also for the encouragement in Section 1.5 of the cookbook to buck up and file this ticket! :)

[Andrew Stevenson (andrew-n1by9anq9)]

The issue is that networking job changed from a task to a..umm...non-task?...between precise and quantal. Have a look at:

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/ifupdown/precise/view/head:/debian/ifupdown.networking.upstart

vs

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/ifupdown/quantal/view/head:/debian/ifupdown.networking.upstart

That breaks upstart jobs depending on "start on stopped networking". I'm still looking for the equivalent that hopefully doesnt require different upstart files depending on the ubuntu version. I would guess that "static-network-up" is not quite the same as non static networking (DHCP interfaces perhaps?) will still be in flux.