From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Clemens Buchacher <drizzd@aon.at>, Jeff King <peff@peff.net>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] t5570: fix forwarding of git-daemon messages via cat
Date: Thu, 26 Apr 2012 23:10:26 +0200 [thread overview]
Message-ID: <4F99B9C2.7090805@in.waw.pl> (raw)
In-Reply-To: <4F99B777.4020103@kdbg.org>
On 04/26/2012 11:00 PM, Johannes Sixt wrote:
> The shell function that starts git-daemon wants to read the first line of
> the daemon's stderr to ensure that it started correctly. Subsequent daemon
> errors should be redirected to fd 4 (which is the terminal in verbose mode
> or /dev/null in quiet mode). To that end the shell script used 'read' to
> get the first line of output, and then 'cat &' to forward everything else
> in a background process.
>
> The problem is, that 'cat >&4 &' does not produce any output because the
> shell redirects a background process's stdin to /dev/null. To have this
> command invocation do anything useful, we have to redirect its stdin
> explicitly (which overrides the /dev/null redirection).
>
> The shell function connects the daemon's stderr to its consumers via a
> FIFO. We cannot just do this:
>
> read line <git_daemon_output
> cat <git_daemon_output >&4 &
>
> because after the first redirection the pipe is closed and the daemon
> could receive SIGPIPE if it writes at the wrong moment. Therefore, we open
> the readable end of the FIFO only once on fd 7 in the shell and dup from
> there to the stdin of the two consumers.
>
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Beautiful explanation. Thanks!
I can confirm that this fix works for me.
-
Zbyszek
next prev parent reply other threads:[~2012-04-26 21:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 8:44 [PATCH] t5570: forward git-daemon messages in a different way Zbigniew Jędrzejewski-Szmek
2012-04-14 12:13 ` Clemens Buchacher
2012-04-14 12:21 ` Clemens Buchacher
2012-04-16 15:43 ` Zbigniew Jędrzejewski-Szmek
2012-04-16 17:09 ` Junio C Hamano
2012-04-16 21:22 ` Clemens Buchacher
2012-04-16 22:06 ` Zbigniew Jędrzejewski-Szmek
2012-04-17 15:43 ` Junio C Hamano
2012-04-16 17:42 ` Jeff King
2012-04-16 22:44 ` Clemens Buchacher
2012-04-19 6:03 ` Jeff King
2012-04-19 6:58 ` Johannes Sixt
2012-04-26 13:01 ` Jeff King
2012-04-26 18:16 ` Johannes Sixt
2012-04-26 19:55 ` Clemens Buchacher
2012-04-26 21:00 ` [PATCH] t5570: fix forwarding of git-daemon messages via cat Johannes Sixt
2012-04-26 21:10 ` Zbigniew Jędrzejewski-Szmek [this message]
2012-04-27 7:59 ` Jeff King
2012-04-27 15:02 ` Junio C Hamano
2012-04-27 7:55 ` [PATCH] t5570: forward git-daemon messages in a different way Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F99B9C2.7090805@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).