shell redirection magic broke boot in 1.1

[Arkadiusz Miśkiewicz]

#619269 fix in 1.1 broke boot on my system.

It reports "/proc/self/fd/8[1]: <&8- : illegal file descriptor name" and that's all from booting process. It doesn't continue.

/bin/sh is pdksh here.

[Johan Kiviniemi (ion)]

Scott,

Shouldn’t

  NIH_ZERO (nih_io_printf (io, "exec <&%d-\n", fds[0]));

be

  NIH_ZERO (nih_io_printf (io, "exec %d<&-\n", fds[0]));

?

[Scott James Remnant (scott)]

Yes, that looks almost certainly wrong; I guess dash + bash simply
don't care - I'll get this fixed and release a 1.2 bpb

2011/3/22 Johan Kiviniemi <email address hidden>:
> Scott,
>
> Shouldn’t
>
>  NIH_ZERO (nih_io_printf (io, "exec <&%d-\n", fds[0]));
>
> be
>
>
>  NIH_ZERO (nih_io_printf (io, "exec %d<&-\n", fds[0]));
>
> ?
>
> ** Changed in: upstart
>       Status: New => Confirmed
>
> --
> You received this bug notification because you are a member of Upstart
> Developers, which is subscribed to upstart .
> https://bugs.launchpad.net/bugs/739984
>
> Title:
>  shell redirection magic broke boot in 1.1
>
> Status in Upstart:
>  Confirmed
>
> Bug description:
>  #619269 fix in 1.1 broke boot on my system.
>
>  It reports "/proc/self/fd/8[1]: <&8- : illegal file descriptor name"
>  and that's all from booting process. It doesn't continue.
>
>  /bin/sh is pdksh here.
>

[Johan Kiviniemi (ion)]

In doesn’t seem to work in dash either. Seems like a bashism.

% dash -c 'exec <&9-; ls -l /proc/self/fd/9' 9<&1
dash: Syntax error: Bad fd number

% bash -c 'exec <&9-; ls -l /proc/self/fd/9' 9<&1
ls: cannot access /proc/self/fd/9: No such file or directory

% zsh -c 'exec <&9-; ls -l /proc/self/fd/9' 9<&1
zsh:1: file number expected

[Scott James Remnant (scott)]

Weird, I have no idea how "make check" passes then ;-)

Oh, yes I do ... /bin/sh is actually "bash" on Google machines - d'oh

2011/3/22 Johan Kiviniemi <email address hidden>:
> In doesn’t seem to work in dash either. Seems like a bashism.
>
> % dash -c 'exec <&9-; ls -l /proc/self/fd/9' 9<&1
> dash: Syntax error: Bad fd number
>
> % bash -c 'exec <&9-; ls -l /proc/self/fd/9' 9<&1
> ls: cannot access /proc/self/fd/9: No such file or directory
>
> % zsh -c 'exec <&9-; ls -l /proc/self/fd/9' 9<&1
> zsh:1: file number expected
>
> --
> You received this bug notification because you are a member of Upstart
> Developers, which is subscribed to upstart .
> https://bugs.launchpad.net/bugs/739984
>
> Title:
>  shell redirection magic broke boot in 1.1
>
> Status in Upstart:
>  Fix Released
>
> Bug description:
>  #619269 fix in 1.1 broke boot on my system.
>
>  It reports "/proc/self/fd/8[1]: <&8- : illegal file descriptor name"
>  and that's all from booting process. It doesn't continue.
>
>  /bin/sh is pdksh here.
>

[Fiodor Kupchik (ferimy)]

It seems I've run into this recently. I've tried to upgrade to ubuntu oneiric on OpenVZ VPS machine and after all the boot process became broken. The only thing I could see in the list of procs is

/bin/sh -e /proc/self/fd/9

and after all services start but not networking. Not sure this is it but very similar situation.