On Sat, Apr 25, 2015 at 12:14:44PM -0700, enh wrote: > what's the plan wrt SIGPIPE? the desktop is pretty inconsistent. many > (but not all) commands install a signal handler that does _exit(0). > others (coreutils 8.21's ls, say) do nothing. normally "what you do > about SIGPIPE" isn't a problem but on Android that leads to a crash > report and people filing "ls crashed" bugs against me. (our default > shell PS setup is also noisy about crashes.)
Why not just *block* SIGPIPE (with sigprocmask) so that the write returns an error (EPIPE) and the program applies the same logic it would for any other write error? Rich _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
