[Bug 928309] Re: State target of SIGTERM more precisely

[James Hunt]

Thank you for reporting this issue.

Since this also affects upstart-events(7), I'm marking this as affecting
Upstart in Ubuntu.

** Also affects: upstart (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: upstart-cookbook
       Status: New => Confirmed

** Changed in: upstart (Ubuntu)
       Status: New => Confirmed

** Changed in: upstart-cookbook
     Assignee: (unassigned) => James Hunt (jamesodhunt)

** Changed in: upstart (Ubuntu)
     Assignee: (unassigned) => James Hunt (jamesodhunt)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/928309

Title:
  State target of SIGTERM more precisely

Status in The Upstart Cookbook:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  The line "The SIGTERM signal is sent to the main process. See
  signal(7)." in section "Stopping a Job" [1] is not precise.

  The SIGTERM signal is sent to the process group, if the group can be
  determined. This means that all processes belonging to this service
  will receive the SIGTERM signal.

  
  [1] http://upstart.ubuntu.com/cookbook/#id106

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart-cookbook/+bug/928309/+subscriptions