From: Romain Francoise <romain@orebokech.com>
Subject: Re: Network issues
Date: Tue, 11 Apr 2006 18:57:38 +0200 [thread overview]
Message-ID: <87wtdwnj7h.fsf@pacem.orebokech.com> (raw)
In-Reply-To: <27020.1142987315@olgas.newt.com> (Bill Wohler's message of "Tue, 21 Mar 2006 16:28:35 -0800")
Bill Wohler <wohler@newt.com> writes:
> It seems that Emacs is caching its network address and thereby
> confusing itself.
I don't think it does... what you're seeing might be due to a change in
your DNS servers: if you get the new address via DHCP on the new network
then you'll probably get new DNS servers, and the libc resolver caches
them by default.
If that's the problem you just need to install glibc's nscd daemon and
run `nscd -i hosts' to force the daemon the reload resolv.conf.
--
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
| ever free! --Bryan W. Procter
next prev parent reply other threads:[~2006-04-11 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 0:28 Bill Wohler
2006-04-11 16:08 ` Lars Magne Ingebrigtsen
2006-04-11 16:57 ` Romain Francoise [this message]
2006-04-11 18:05 ` Bill Wohler
2006-04-14 18:50 ` Bill Wohler
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=87wtdwnj7h.fsf@pacem.orebokech.com \
--to=romain@orebokech.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;
as well as URLs for NNTP newsgroup(s).