git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] unblock and unignore SIGPIPE

From
Patrick Reynolds <patrick.reynolds@github.com>
Date
Aug 22, 2014, 05:40 UTC
Message-ID
<CAJrMUs_P25m68F_Rv4beSUiGB0uybbP=hBGULzZaefiW4gh=XQ@mail.gmail.com>
In-Reply-To
<20140818011445.GA22180@dcvr.yhbt.net>
On Sun, Aug 17, 2014 at 8:14 PM, Eric Wong <normalperson@yhbt.net> wrote:
> But unicorn would ignore SIGPIPE it if Ruby did not; relying on SIGPIPE
> while doing any multiplexed I/O doesn't work well.

Exactly. Callers block SIGPIPE for their own legitimate reasons, but they don't consistently unblock it before spawning a git subprocess that needs the default SIGPIPE behavior. Easier to fix it in git than in every potential caller.

--Patrick
Previous: Eric WongNext: Junio C Hamano
Message 3 of 8 in “unblock and unignore SIGPIPE”
  1. unblock and unignore SIGPIPEPatrick Reynolds, Aug 15, 2014
  2. Eric WongAug 18, 2014
  3. Patrick ReynoldsAug 22, 2014
  4. Junio C HamanoSep 16, 2014
  5. Jeff KingSep 17, 2014
  6. Junio C HamanoSep 17, 2014
  7. Patrick ReynoldsSep 18, 2014
  8. Junio C HamanoSep 18, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.