ProcServ fills our log files with @@@ Got a sigPipe signal: Did the child close its tty? messages for no obvious reasons. Sometimes multiple times per second.
The IOCs are still healthy and communicate with procServ without problems.
The code in ProcServ does nothing upon sigPipe but sending the message.
I wonder why it is there and why procServ does not simply ignore sigPipe.
ralphlange
commented
3 years ago
ProcServ fills our log files with
@@@ Got a sigPipe signal: Did the child close its tty?messages for no obvious reasons. Sometimes multiple times per second. The IOCs are still healthy and communicate with procServ without problems. The code in ProcServ does nothing upon sigPipe but sending the message. I wonder why it is there and why procServ does not simply ignore sigPipe.