[Bug 757244] Re: Jobs won't start using pdsh if script fd >= 10

[Jacek Konieczny]

Attaching a quick hack (not an elegant solution) which solves the
problem for me (the script fd is dup2()ed to fd #3 in the child
process).

** Patch added: "upstart-script_fd.patch"
   https://bugs.launchpad.net/upstart/+bug/757244/+attachment/2022750/+files/upstart-script_fd.patch

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/757244

Title:
  Jobs won't start using pdsh if script fd >= 10

Status in Upstart:
  New
Status in PLD Linux Distribution:
  New

Bug description:
  After upgrading Upstart to 1.2 I found some of my jobs not starting
  (exiting with code '127'). After some investigation I found out that
  Upstart prepends 'exec 10<&-' to the scripts of the failing jobs, to
  close the input pipe. The problem is this won't work for some POSIX
  shells, which can handle only single-digit file descriptors this way.
  This works for the big and heavy bash, but won't for under PDKSH (used
  as /bin/sh in e.g. PLD Linux).

  Can upstart be made to use some fixed file descriptor for this task?
  e.g. '3'?