Uhhmm... that sounds like a violent solution to me. It would make sense
if I knew that the potential programmers are top-notch UNIX experts.
Otherwise, I'm not sure they will appreciate me killing their process.
The point about this is to give the impression that I'm doing things
right, and the hardware fails.
But it's a nice take on the subject. ;)
Eli
Oron Peled wrote:
Another strategy is to throw SIGPIPE at the relevant processes:
* Con: it is usually expected upon write(2) not read(2) et-al.
* Pros:
- At least for write(2) the semantics is natural -- no more writes
on this file descriptor.
- Kills the offending process by default.
- Process may catch it in a signal handler (easy to write some
global cleanup + exit code)
Cheers,
--
Web: http://www.billauer.co.il
_______________________________________________
Haifux mailing list
[email protected]
http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
