[PATCH] Custom resolv.conf

Ulrich Drepper drepper@redhat.com
Wed Sep 15 17:29:00 GMT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michal Svec wrote:

> If you mean when is this useful, then for instance in situations when
> you'd like to look up some hostname using the glibc built-in resolver, but
> without messing up the config files (think of the network configuration,
> where you would like to resolve names before anything is actually
> written).

Then use host, dig, nslookup.  They don't use the glibc resolver.

I don't like this customization one bit since it introduces yet another
error source.  A program's behavior is different if a local resolv.conf
is used or if nscd is running.  This just means maintenance nightmares.
 And no, using "but it is done for file XYZ" is no argument.  I wouldn't
add these envvars today either.  Early mistakes.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBSHvf2ijCOnn/RHQRAqFVAKDJ1B8RCHyc1BfYEt5jc/N7BnmQwwCgrE6Q
/q0LoCy6UCbXx4sXIc0V5p0=
=2Nyv
-----END PGP SIGNATURE-----



More information about the Libc-alpha mailing list