Recovery possible from signal aborted write(2) ?

[Tim Smith]

****** WARNING: KLUDGE ALERT! KLUDGE ALERT! KLUDGE ALERT! *******

If you have a kernel that leaves u readable by the process,
then you can try looking at u.u_count to see how many characters
were not transfered.  You have to read this directly, though,
because going through /dev/kmem will trash this variable.

Also, this may not work on signals gernerated from the tty, because
in attempting to flush the output buffer, it may screw u_count.

If you have source, you could change the routine that flushes the
output buffer to preserve u_count.

By the way, is there any reason to not have u directly readable?
It's been that way for about two years here at cithep, but I think
only two or three people know it!
-- 
Tim Smith		ihnp4!cithep!tim  or  ihnp4!wlbr!callan!tim