Hi Steve, The changes already will stop a job that was started manually (since we fall through the 'if' tests and invoke "$COMMAND "$JOB", where $COMMAND is 'stop').
I've tweaked the logic for restart such that for disabled jobs the behaviour is now: - if the job is running, 'upstart-job start' will just exit (since nothing to do). - if the job is not running, 'upstart-job start' will just exit (since job is disabled). - if the job is running, 'upstart-job stop' will stop the job (since job was forced into start state). - if the job is not running, 'upstart-job stop' will just exit (since nothing to do). - if the job is running, 'upstart-job restart' will restart the job (since job was forced into start state and admins will expect this behaviour). - if the job is not running, 'upstart-job restart' will just exit (since job is disabled). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974147 Title: /lib/init/upstart-job should not start/restart a job which is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/974147/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
