Subject: Re: re-reading /etc/resolv.conf on change
To: Jason Thorpe <firstname.lastname@example.org>
From: Luke Mewburn <lukem@NetBSD.org>
Date: 01/07/2004 08:58:16
Content-Type: text/plain; charset=us-ascii
On Tue, Jan 06, 2004 at 09:21:52AM -0800, Jason Thorpe wrote:
| On Jan 5, 2004, at 3:38 PM, Luke Mewburn wrote:
| >How's this for an solution?
| This seems far more complicated than necessary. Having to touch=20
| nsswitch.conf seems non-obvious. After all, you already edited the=20
| file you care about!
| I don't really see this as a better solution than the resolver simply=
| detecting the condition itself and coping.
I'm leaning towards the dns backend reloading resolv.conf as
That said, I may still implement the nsswitch init method concept if
it turns out to be useful.
| > Implement an optional "init" method for each nsswitch
| > backend database (YP, DNS, files), which is called
| > whenever nsdispatch reloads /etc/nsswitch.conf.
| >This provides each database type an opportunity to (re)initialize
| >itself, which may be useful to simplify various implementations
| >that retain state.
| >Then end user then just "touchs" /etc/nsswitch.conf to force a
| >reinit of the method lookups used by nsdispatch (as currently occurs)
| >and a reinit of the database backend.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----