From: Jeff King <peff@peff.net>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: Dave Zarzycki <zarzycki@apple.com>, git@vger.kernel.org
Subject: Re: [PATCH] Do not log unless all connect() attempts fail
Date: Wed, 13 Jul 2011 17:06:36 -0400 [thread overview]
Message-ID: <20110713210636.GF31965@sigill.intra.peff.net> (raw)
In-Reply-To: <CABPQNSaPXmHE1qECUbG9oWU43HbAXxAY42T1P=MNHgkkWM936w@mail.gmail.com>
On Wed, Jul 13, 2011 at 11:23:33AM +0200, Erik Faye-Lund wrote:
> > static int git_tcp_connect_sock(char *host, int flags)
> > {
> > + struct strbuf error_message = STRBUF_INIT;
> > int sockfd = -1, saved_errno = 0;
> > const char *port = STR(DEFAULT_GIT_PORT);
> > struct addrinfo hints, *ai0, *ai;
> > @@ -225,11 +226,8 @@ static int git_tcp_connect_sock(char *host, int flags)
> > }
> > if (connect(sockfd, ai->ai_addr, ai->ai_addrlen) < 0) {
> > saved_errno = errno;
> > - fprintf(stderr, "%s[%d: %s]: errno=%s\n",
> > - host,
> > - cnt,
> > - ai_name(ai),
> > - strerror(saved_errno));
> > + strbuf_addf(&error_message, "%s[%d: %s]: errno=%s\n",
> > + host, cnt, ai_name(ai), strerror(saved_errno));
> > close(sockfd);
> > sockfd = -1;
> > continue;
> > @@ -242,11 +240,13 @@ static int git_tcp_connect_sock(char *host, int flags)
> > freeaddrinfo(ai0);
> >
> > if (sockfd < 0)
> > - die("unable to connect a socket (%s)", strerror(saved_errno));
> > + die("unable to connect to %s:\n%s", host, error_message.buf);
> >
>
> This kills the output from the case where "sockfd < 0" evaluates to
> true for the last entry in ai, no (just above your second hunk), no?
> In that case errno gets copied to saved_errno, and the old output
> would do strerror(old_errno), but now you just print the log you've
> gathered, and don't even look at saved_errno.
But that's OK, because the value of that saved_errno is in the gathered
log, isn't it? So the output is not identical, but IMHO it's much
better. It's gone from:
$ git fetch git://example.com/foo
example.com[0: 192.0.32.10]: errno=Connection timed out
example.com[0: 2620:0:2d0:200::10]: errno=Network is unreachable
fatal: unable to connect a socket (Network is unreachable)
to:
$ git fetch git://example.com/foo
fatal: unable to connect to example.com:
example.com[0: 192.0.32.10]: errno=Connection timed out
example.com[0: 2620:0:2d0:200::10]: errno=Network is unreachable
IMHO, the "Network is unreachable" at the end of the first one is just
noise; it's a duplicate of what was already printed, and it may not be
the errno value that is most interesting to you.
> If this is intentional then you should probably kill the saved_errno
> variable also, it's rendered pointless by this patch.
That is sensible, though, I think.
-Peff
next prev parent reply other threads:[~2011-07-13 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 16:28 [PATCH] Do not log unless all connect() attempts fail Dave Zarzycki
2011-07-13 9:23 ` Erik Faye-Lund
2011-07-13 20:39 ` Junio C Hamano
2011-07-13 21:06 ` Jeff King [this message]
2011-07-13 22:29 ` Erik Faye-Lund
2011-07-13 23:43 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 17:52 Dave Zarzycki
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=20110713210636.GF31965@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=zarzycki@apple.com \
/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