in reply to Re^2: Detect whether a writeable filehandle has closed?
in thread Detect whether a writeable filehandle has closed?

As said, you get the SIPGPIPE immediately after the first unsuccessful write, so you may want to keep your amount of lines short for each write.

If you have control of the child you could make it send a HUP or USR1 to its parent after closing the file handle.

Update: Oh I see you haven't, a compiled C program... hm. A wrapper, maybe?

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
  • Comment on Re^3: Detect whether a writeable filehandle has closed?

In Section Seekers of Perl Wisdom