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

[Scott James Remnant]

Thanks for the patch, actually I don't think that's a hacky way to do
things, but there is an issue if the writing end of the error pipe
happens to have that file descriptor - you could close it in the dup2()
- I'll commit an expanded version of the 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:
  Triaged
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'?