Lui Fungsin scripsit:
> For example, a typical C program will ignore SIGPIPE, and check for
> return code for every write/fprintf.
Most C programs don't seem to ignore SIGPIPE; in fact, the reason it exists
is to allow programs to be killed silently when their output is no longer
wanted by the next pipeline step. Try <random-command> | more, get a page
of output, and hit 'q'; very few programs will report EPIPE ("svn log"
is the only one I know of).
--
A rabbi whose congregation doesn't want John Cowan
to drive him out of town isn't a rabbi, http://www.ccil.org/~cowan
and a rabbi who lets them do it [EMAIL PROTECTED]
isn't a man. --Jewish saying
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
