Program terminated with signal sigpipe broken pipe

Arvid SIGPIPE was invented by Unix people, to solve a problem they were having in their environment in which filter programs are extremely common, All we have to do is read the boot scripts that bring up the system. Show 1 more comment. Update Consider a pipeline A B C. Run a pipeline like cat B more and in another terminal window, attach a debugger to B and put a breakpoint inside the B signal handler.

Charlie Martin Charlie Martin k 23 23 gold badges silver badges bronze badges. Without this it takes up to one cycle of the copy program for each of N elements of the pipe to kill the pipeline, and causes the input side to generate N lines that never reach the end. This answer is incorrect. You don't need to write a C program to test it, just run cat head , and pkill head in a separate terminal.

You'll see that cat happily lives on waiting in its read —only when you type something in and press enter does cat die with a broken pipe, exactly because it tried to write output. I cannot reproduce that behavior at all and am not actually sure why I accepted this in the first place — Shea Levy.

Show 6 more comments. Ankur Agarwal Ankur Agarwal Machine info: Linux 3. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Linked Related 3. The default behaviour for this signal is to end the process. I sort of experienced the same problem and it let me to this SO post. The reason was that nginx's temp dir had a permission problem. Details here on how to fix and more here. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 8 years, 3 months ago. Active 2 years, 7 months ago. Viewed 89k times. Improve this question. Add a comment. Active Oldest Votes. Producer with. MockingJayWong mentioned this issue Aug 2, Recovery takes too long after stopping and restarting a broker in a cluster Broker with Kerberos: some produce calls took 1 minute to finish JoakimBlach mentioned this issue Apr 30, It is crashed ,when use method of the producer in the thread Lasuerte mentioned this issue Jul 24, Furuta-Masakazu-quick mentioned this issue Sep 29, Producer detects "All broker connections are down" when rolling restarts Port to BoringSSL.

Question: sending single message with no delay Duplicate message from RDKafka High CPU usage in librdkafka1. Throughput decrease badly while broker number increase. RdKafka::Producer parses aws kafka broker reporting segment errors when the cluster information is retrieved after a few minutes Sign up for free to join this conversation on GitHub. Already have an account?