Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

procServ prints "@@@ Got a sigPipe signal: Did the child close its tty?" all the time #43

Open
dirk-zimoch opened this issue Nov 30, 2020 · 1 comment · May be fixed by #52
Open

procServ prints "@@@ Got a sigPipe signal: Did the child close its tty?" all the time #43

dirk-zimoch opened this issue Nov 30, 2020 · 1 comment · May be fixed by #52

Comments

@dirk-zimoch
Copy link
Contributor

dirk-zimoch commented Nov 30, 2020 •
edited
Loading

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
Copy link
Owner

Good question.

This was referenced Apr 15, 2021
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ignore sigpipe dirk-zimoch/procServ
2 participants
@ralphlange @dirk-zimoch