Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Cc: Magnus Henoch <magnus.henoch@gmail.com>
Subject: Re: dns.el: forget DNS servers in new network
Date: Thu, 30 Jan 2014 14:19:15 -0800	[thread overview]
Message-ID: <87iot1dsf0.fsf@building.gnus.org> (raw)
In-Reply-To: <87bo21u3v7.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Sun, 03 Nov 2013 06:22:20 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> MH> Thus the patch below.  It checks whether the names and IP addresses of
> MH> all network interfaces have changed, and if so, rereads /etc/resolv.conf
> MH> instead of using the value of dns-servers.  What do you think about it?
>
> I like it.  I wonder if it can be used more generally to find out if the
> network has changed, a pretty common mobile case that can produce
> connection timeouts.

Yeah, it's a good idea.  Gnus should kill off all network connections
when the IP address changes.

It's not a 100% solution (you may be tethered behind a device that
changes address, and they you won't discover the situation because your
own IP address doesn't change), but it's better than nothing.

However, I wonder whether this could be done more generally?  That is,
allow functions to "register" actions to be done when the IP address
changes, so that we don't have to duplicate this code in several
packages... 

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2014-01-30 22:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 21:02 Magnus Henoch
2013-11-03 11:22 ` Ted Zlatanov
2014-01-30 22:19   ` Lars Ingebrigtsen [this message]
2014-02-02 21:56     ` Leonidas Tsampros
2014-02-02 22:17       ` Julien Danjou
2014-01-31 23:53 ` Lars Ingebrigtsen

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=87iot1dsf0.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=magnus.henoch@gmail.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).