This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Custom resolv.conf


On Wed, 15 Sep 2004, Ulrich Drepper 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.

Well, then I somehow do not get the reason why we have resolver in glibc 
at all, if it's not supposed to be used?

> 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.

What do you exactly mean with "maintenance nightmare"? Customization could 
be IMHO only a good thing ...

Regards
Michal
--
Michal Svec
msvec@suse.cz


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]