From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Kim Gybels <kgybels@infogroep.be>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH 2/2] daemon: graceful shutdown of client connection
Date: Fri, 13 Apr 2018 15:03:21 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1804131440100.65@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (raw)
In-Reply-To: <20180412210757.7792-3-kgybels@infogroep.be>
Hi Kim,
On Thu, 12 Apr 2018, Kim Gybels wrote:
> On Windows, a connection is shutdown when the last open handle to it is
> closed. When that last open handle is stdout of our child process, an
> abortive shutdown is triggered when said process exits. Ensure a
> graceful shutdown of the client connection by keeping an open handle
> until we detect our child process has finished. This allows all the data
> to be sent to the client, instead of being discarded.
Nice explanation!
> @@ -928,13 +931,13 @@ static void handle(int incoming, struct sockaddr *addr, socklen_t addrlen)
> }
>
> cld.argv = cld_argv.argv;
> - cld.in = incoming;
> + cld.in = dup(incoming);
At first I was worried that somebody might want to remove this in the
future, but then I saw this line (which also calls dup()):
> cld.out = dup(incoming);
>
> if (start_command(&cld))
> logerror("unable to fork");
> else
> - add_child(&cld, addr, addrlen);
> + add_child(&cld, addr, addrlen, incoming);
> }
>
> static void child_handler(int signo)
Nice work!
I wonder whether you found a reliable way to trigger this? It would be
nice to have a regression test for this.
Ciao,
Dscho
next prev parent reply other threads:[~2018-04-13 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 21:07 [PATCH 0/2] Fix early EOF with GfW daemon Kim Gybels
2018-04-12 21:07 ` [PATCH 1/2] daemon: use timeout for uninterruptible poll Kim Gybels
2018-04-13 12:36 ` Johannes Schindelin
2018-04-15 17:08 ` Kim Gybels
2018-04-18 21:16 ` Johannes Schindelin
2018-04-15 21:54 ` Junio C Hamano
2018-04-15 22:16 ` Junio C Hamano
2018-04-18 21:07 ` Johannes Schindelin
2018-04-18 21:51 ` Junio C Hamano
2018-04-19 21:33 ` Kim Gybels
2018-04-19 23:18 ` Junio C Hamano
2018-04-12 21:07 ` [PATCH 2/2] daemon: graceful shutdown of client connection Kim Gybels
2018-04-13 13:03 ` Johannes Schindelin [this message]
2018-04-15 20:21 ` Kim Gybels
2018-04-18 21:48 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1804131440100.65@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kgybels@infogroep.be \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).