Detecting the close() of named pipes

jeffthewookiee has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Detecting the close() of named pipes by shmem (Chancellor) on Aug 23, 2006 at 15:19 UTC
On which side of the pipe did you register a `$SIG{PIPE}` handler? If the reader closes the pipe, the writer to a pipe gets a SIGPIPE; if the writer closes it, the reader gets EOF. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply] [d/l]
Re^2: Detecting the close() of named pipes by betterworld (Curate) on Aug 23, 2006 at 18:53 UTC
the writer to a pipe gets a SIGPIPE Or, if SIGPIPE is ignored, the writer gets an EPIPE error.	[reply]
Re: Detecting the close() of named pipes by innominate (Beadle) on Aug 23, 2006 at 15:20 UTC
Have you tried the -e file test? Example: `open(my $z, '\| more'); # stupid call, just an example! print ("Exists: ", -e $z, "\n"); close($z); print ("\nExists: ", -e $z, "\n");` [download] Should return: `Exists: 1 Exists:` [download]	[reply] [d/l] [select]
Re^2: Detecting the close() of named pipes by jeffthewookiee (Sexton) on Aug 23, 2006 at 16:46 UTC
When I close() the named pipe, it seems to leave the files there though... they still Exist. I'm using POSIX:mknod to make it.	[reply]
Re^3: Detecting the close() of named pipes by shmem (Chancellor) on Aug 23, 2006 at 16:59 UTC
If you don't remove them, there they are. As usual ;-) Named pipes are files, you have to do the cleanup yourself, as opposed to anonymous pipes. The latter are reaped by the OS. See pipe for those. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]