Quote:
Originally Posted by stoduk
I hadn't realised that the pipe error might be overflow rather than disconnection. Does it make sense that the problem never resolves?
|
Standard outputs are pipes. What a process does when it fails to write to a pipe is up to the process. A process can report a "failure to write" when it really had a "failure to write within some delay." The process can fail or it can wait and try again. Dealing with transients is hard, so most people do the first: die.
TBH, I would be surprised if OSX fails in this way. Its underlying OS is based on BSD unix, and there is almost no chance that the underlying OS wouldn't handle throttling correctly. On the other hand, it is possible that the terminal application throttles by reporting errors instead of by waiting. I don't know.
