------- Comment From [email protected] 2014-10-09 17:08 EDT------- (In reply to comment #7) > do you need to have scripts being fixed for you? Yes, need to fix/enhance Upstart for me and other customers who accidentally type in and run a job at command line, or start the job from crontab, because once that was done (i.e. the job was started from outside of the Upstart), Upstart will be unable to stop/restart the job.
> are daemons missing permissions to execute properly and retrieve infos ? No, the Upstart daemon has all the permission to do the expected things (stop/restart a job). It simply just can not function as what I expect. Perhaps some people just think not Upstart's business to handle (stop/restart) the process which it did not ever run? I believe the problem was clearly described at the defect opening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337407 Title: Upstart can NOT handle service/job started by others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1337407/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
