BusyBox 'ash' should reset SIGQUIT action of its children (Bug)

[Denys Vlasenko]

On Fri, Jul 15, 2016 at 9:49 AM, Kang-Che Sung <explorer09 at gmail.com> wrote:
> I recently discovered this bug, but since BusyBox website is offline
> for now, I think I'll report here first.
>
> Test case (try on a freshly logged-in tty where busybox ash isn't the
> default shell):
>
>     $ bash
>     $ exec bash
>     $ yes >/dev/null
>     $ # (Press Ctrl+\ )
>     $ dash
>     $ exec dash
>     $ yes >/dev/null
>     $ # (Press Ctrl+\ )
>     $ busybox ash
>     $ exec busybox ash
>     $ yes >/dev/null
>     $ # (Press Ctrl+\ )
>
> Actual result: The last `yes` command (the one started after `exec
> busybox ash`) doesn't die.
>
> Expected result: All three `yes` commands should die with SIGQUIT.

Thanks. Turns out SIGQUIT is left SIG_IGNed if command
is executed via "exec CMD".
Fixed in git now.