Upstart does not reload properly .conf files that use "instance" feature
Bug #611082 reported by
Christian Hudon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I renamed /etc/init/
Maybe upstart does not handle properly reload for .conf files which use the "instance" feature? I am running upstart 0.6.5-6 on Ubuntu 10.04 LTS.
To post a comment you must log in.
Actually Upstart reloads such .conf file just fine, what you've probably missed is that Upstart will not use the new .conf until all existing instances have stopped.
This is because the new .conf may change such things as locking between the instances, or criterion for instance creation, that would affect any running instances.
It's exactly the same process that ensures that a running job uses the *previous* "post-stop" script, rather than a new one, if the .conf is changed while it's running