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.
bash and dash both show the same behavior that the commands we start in
them can get killed with SIGQUIT. But BusyBox ash shows a wrong
behavior that the ignore action of SIGQUIT get carried to child
processes while it shouldn't.
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
