> I found that the standard Linux in.popd was getting a signal (SIGPIPE) that
> it wasn't expecting when the customer aborted his Netscape download of a
> large file (wasn't expecting a > 1 Meg file, I guess). This signal causes
> the daemon to exit unexpectedly. (Why this signal is generated, I didn't
> explore too far).
I believe SIGPIPE happens when you try to write to a pipe that has been
closed, but it may happen when there are bytes queued on a pipe that gets
closed. It's one of those things that isn't documented anywhere handy (or,
perhaps, anywhere at all).