On Mon, 2003-04-14 at 20:08, Keegan Quinn wrote:
> If we're going to have /run/resolver, why not use /run/resolver/resolv.conf?
Fine with me. Any objections?
--
Thomas Hood <[EMAIL PROTECTED]>
On Monday 14 April 2003 02:36 am, Thomas Hood wrote:
> Proposal: Implementation steps for dynamic resolver configuration
[snip]
> * New "resolver" package includes /etc/init.d/resolver which
> generates /run/resolv.conf from /run/resolver/interface/*
> and does a run-parts on /etc/resolver/up
Proposal: Implementation steps for dynamic resolver configuration
Assuming that it is impossible to update networking daemons and
DNS caches simultaneously with providing the infrastructure for
dynamic resolver configuration, we need a plan for doing it in
stages.
Each of the following steps shou
On Sun, 2003-04-13 at 19:25, Jeremie Koenig wrote:
>> * Make the latter scripts get their resolv.conf data from stdin
>> instead of from the /run/network/resolv.d/* files
>
> This is important. It must be possible to control which nameservers go
> to which recipient script. For instance bind must
On Sun, Apr 13, 2003 at 03:54:58PM +0200, Thomas Hood wrote:
> In the following, where you write '/etc/resolv-update.d' I guess you
> meant to say '/etc/network/resolv-update.d' since /etc/network is
> where ifupdown stores its configuration files.
Sure.
> > Underlying programs to configure inter
On Sat, 2003-04-12 at 02:34, Jeremie Koenig wrote:
> Sounds quite good. But I have a suggestion about going one step further:
> include the whole thing into ifupdown.
[...]
In the following, where you write '/etc/resolv-update.d' I guess you
meant to say '/etc/network/resolv-update.d' since /etc/n
(sorry, i have easy enthusiasm, especially at 2:30 am ;)
On Fri, Apr 11, 2003 at 10:39:46PM +0200, Thomas Hood wrote:
> TODO for etc/resolv.conf
> Overview
> * /etc/resolv.conf -> /run/resolv.conf
> * Networking daemon pidfiles go in /run/
> * Resolv.conf-like files
7 matches
Mail list logo
