From: Alan Mackenzie <acm@muc.de>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: Help with bzr access, please!
Date: Tue, 19 Oct 2010 19:28:23 +0000 [thread overview]
Message-ID: <20101019192823.GC2027@muc.de> (raw)
In-Reply-To: <87mxqavww7.fsf@turtle.gmx.de>
Hi, Sven,
On Tue, Oct 19, 2010 at 08:51:36PM +0200, Sven Joachim wrote:
> Am 19.10.2010 um 20:50 schrieb Alan Mackenzie:
> > On Tue, Oct 19, 2010 at 12:17:18AM +0200, Andreas Schwab wrote:
> >> Alan Mackenzie <acm@muc.de> writes:
> >> > On Sat, Oct 16, 2010 at 09:22:30PM +0200, Andreas Schwab wrote:
> >> >> Please make sure that it resolves to 140.186.70.72 instead of
> >> >> 140.186.70.73.
> >> > $ nslookup bzr.sv.gnu.org
> >> > gives "Address: 140.186.70.72".
> >> And what do you get from "getent ahosts bzr.savannah.gnu.org"?
> > 140.186.70.73 STREAM bzr.savannah.gnu.org
> > 140.186.70.73 DGRAM bzr.savannah.gnu.org
> > 140.186.70.73 RAW bzr.savannah.gnu.org
> > Wierd. Surely nslookup and getent should give the same answers?
> Not necessarily. AFAIK nslookup always contacts a nameserver, whereas
> getent might obtain the IP by other means (e.g. via a hosts(5) file).
That was it! I had an entry for bzr.savannah.gnu.org in my /etc/hosts
(without which there is a 20s delay on every name lookup by SSH; I've
been meaning to debug this for about 3 years, now).
Thanks Sven, thanks Andreas!
> Sven
next prev parent reply other threads:[~2010-10-19 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 19:09 Help with bzr access, please! Alan Mackenzie
2010-10-16 19:22 ` Andreas Schwab
2010-10-16 20:24 ` Alan Mackenzie
2010-10-18 22:17 ` Andreas Schwab
2010-10-19 18:50 ` Alan Mackenzie
2010-10-19 18:51 ` Sven Joachim
2010-10-19 19:28 ` Alan Mackenzie [this message]
2010-10-19 20:42 ` Stefan Monnier
2010-10-19 18:56 ` Chong Yidong
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101019192823.GC2027@muc.de \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=svenjoac@gmx.de \
/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://git.savannah.gnu.org/cgit/emacs.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).