I'm afraid you've misunderstood the semantics here. It's "start on
starting", not "run on starting"; once the job is considered "started"
by upstart, the network-interface job can continue - and unless you
specify 'task', the job is started as soon as the 'script' is running.
You also haven't taken into account here that network-interface has an
'instance'. This means that your job will only block the /first/
network interface. For an example of how to do this currently, see the
network-interface-security job in Ubuntu.
** Changed in: upstart (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099420
Title:
"starting" hook doesn't work as expected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1099420/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
