Re^2: Detect whether a writeable filehandle has closed?

Thank you for that. I think I'd be ok if I got the SIGPIPE instantaneously, but as I said it appears that the signal has to "make its way through the system" before my handler code gets control, by which time I may have written any number of additional lines to the child. :-(

Comment on Re^2: Detect whether a writeable filehandle has closed?

Replies are listed 'Best First'.
Re^3: Detect whether a writeable filehandle has closed? by shmem (Chancellor) on Jan 14, 2021 at 14:56 UTC
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'	[reply]