broken pipes

A broken pipe means that you are writing onto a pipe that has been closed by the other end.

i have unix batch which forks some process
and these processes are communicating each other via pipes.
but sometimes i got too many broken pipe error.
how can i search for the cause of these errors,
is there any item that i should monitor, or is there anyvalues
that i should log to find out the cause of problem?
many resources writes that:
"A broken pipe means that you are writing onto
a pipe that has been closed by the other end."

can anybody suggest a methodology to
to determine the reason why the other end closes the pipe?
how can i search for it in my code?

note down the file descriptors of the pipe

  • comm interface to two process..

check for the push and pull process ( which pumps in and uses the pumped data )
and the corresponding desc...

push process ... need not have the read des opened
and similiarly for
the pull process ... need not have the write des opened ...

check out for that ...
just a thought :wink: