Gnus development mailing list
 help / color / mirror / Atom feed
From: "William M. Perry" <wmperry@kadath.us>
Cc: ding@gnus.org
Subject: Re: Refresh of DNS servers
Date: Wed, 04 Feb 2004 11:58:50 -0500	[thread overview]
Message-ID: <402124CA.2000907@kadath.us> (raw)
In-Reply-To: <bvnlft$1t1$1@quimby.gnus.org>

Ralf Angeli wrote:

>* Derrell Lipman (2004-02-02) writes:
>
>  
>
>>The name servers are typically listed in /etc/resolv.conf which is one of the
>>configuration files for the resolver.  The resolver library [see resolver(3)]
>>which most applications that needs DNS services links with, only reads its
>>configuration files when res_init() is called, which typically occurs only
>>when the very first resolver services are required.  It's likely not gnus
>>that's caching the old nameserver, but rather the resolver library in emacs.
>>Since emacs is still running, the resolver library is not reinitializing.  I
>>don't know of any way to force a reinitialization, although one may exist
>>(some signal, possibly).
>>    
>>
>
>This sounds reasonable.  Does anybody have a hint where I could start
>to look for this stuff?  I grepped the Gnus and Emacs source
>directories for "dns", "res_init" and variations of "nameserv" and
>"resolv" but this didn't yield a usable result (I only found some
>utility functions in `net-utils.el'.  Maybe I missed something?).  I
>also tried to dig into `gnus-group-get-new-news' but got lost
>somewhere in the middle.
>  
>
You would need to make C level changes.  And is (probably?) going to 
vary from OS to OS.  I am pretty sure you can do it on linux by just doing:

if (res_state && (res_state->options & RES_INIT))
{
   res_state->options |= ~RES_INIT;
   res_init();
}

Solaris is similar.  There are also some tricks you could play to notice 
this by enumerating the interfaces and seeing if any of them are 
dynamically assigned.  Hrmm... linux doesn't appear to support that.  
Solaris does though. ;)

-bp



  parent reply	other threads:[~2004-02-04 16:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02  8:25 Ralf Angeli
2004-02-02 14:47 ` Kai Grossjohann
2004-02-02 19:40   ` Ralf Angeli
2004-02-02 21:02     ` Derrell.Lipman
2004-02-03  8:18       ` Ralf Angeli
2004-02-03 14:42         ` Derrell.Lipman
2004-02-04 16:58         ` William M. Perry [this message]
2004-02-05  8:28           ` Ralf Angeli
2004-02-02 16:13 ` Jeremy Maitin-Shepard
2004-02-02 19:40   ` Ralf Angeli
2004-02-02 22:38     ` Jeremy Maitin-Shepard
2004-02-03  7:58       ` Ralf Angeli
2004-02-06 19:32         ` Xavier Maillard

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=402124CA.2000907@kadath.us \
    --to=wmperry@kadath.us \
    --cc=ding@gnus.org \
    /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).