touch-packages team mailing list archive

[Matthew Hawkins <darthmdh@xxxxxxxxx>]

Public bug reported:

When dash is used as /bin/sh and is called with -c to execute commands,
dash doesn't appear to pass signals to the child process.  When the
process spawning dash sends dash a SIGTERM for example, it causes those
subprocesses to never die, and wrecks havoc on servers as tons of
spawned processes get reparented to init and continue to run or get
zombied.

I've seen this problem mentioned in various guises around the internet
(depending on the context of what's spawning dash), and in every case
the supplied "solution" is the same:  stop using dash

e.g. see http://answers.splunk.com/answers/261159/python-eventgenpy-
process-not-killed-when-stopping.html

    debconf-set-selections <<< "dash dash/sh string false"
    dpkg-reconfigure -f noninteractive dash

This has always been the case, you can find examples going back to
Ubuntu 6.10 which first enabled the use of dash as /bin/sh and exists in
at least 14.04 LTS

I'd like to think there's a better solution for this misbehaviour in
dash than to stop using it altogether!

** Affects: dash (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1473000

Title:
  Child processes not reaped when parent dash terminated

Status in dash package in Ubuntu:
  New

Bug description:
  When dash is used as /bin/sh and is called with -c to execute
  commands, dash doesn't appear to pass signals to the child process.
  When the process spawning dash sends dash a SIGTERM for example, it
  causes those subprocesses to never die, and wrecks havoc on servers as
  tons of spawned processes get reparented to init and continue to run
  or get zombied.

  I've seen this problem mentioned in various guises around the internet
  (depending on the context of what's spawning dash), and in every case
  the supplied "solution" is the same:  stop using dash

  e.g. see http://answers.splunk.com/answers/261159/python-eventgenpy-
  process-not-killed-when-stopping.html

      debconf-set-selections <<< "dash dash/sh string false"
      dpkg-reconfigure -f noninteractive dash

  This has always been the case, you can find examples going back to
  Ubuntu 6.10 which first enabled the use of dash as /bin/sh and exists
  in at least 14.04 LTS

  I'd like to think there's a better solution for this misbehaviour in
  dash than to stop using it altogether!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1473000/+subscriptions