config not reloaded if "stop" is interrupted (e.g. with SIGINT)
Bug #1389397 reported by
Eric Herot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
New
|
Undecided
|
Unassigned |
Bug Description
This can happen if, for example, "expect" is mis-specified, causing a confusing situation where stopping the job--and appearing to have all running instances stopped--does not actually cause the config to be reloaded as the documentation says that it should be.
To post a comment you must log in.