Herwin Jan Steehouwer (herwinjs@palet.nl) spake thusly:
> >   Install a Unix signal handler for SIGPIPE. The problem is that
> > whatever's listening to that socket has stopped listening to it,
> > but you're still writing to it.
> 
> I thought Ksock handles this by raising KSocket::closeEvent(KSocker *) ??

  Search me :) I'm just saying what SIGPIPE means. Hmm. Maybe if you got
two in quick succession you could have problems, depending on how the signal
handling works.

-- 

	Jo