On Tue, 4 Nov 2003, Frank Ticheler wrote:

> > Standard or not, it seems to be commonly used all over, judging from a
> > little googling on the subject. I would expect it to support both!
>
> Well, that's possible ofcourse. Ares initializes itself using the order: by
> options (c-api), by resolv.conf and by defaults. So the reading of
> nsswitch.conf shall be added somewhere in this. I also saw that some systems
> use the /etc/host.conf file which can be added as well. I need to check what
> would be the best order to read / check all these files.

Yes, we should try to figure out the best order to check them out and then
make the code do so.

> By the way, the default sequence is "bf" (bind files). I don't know if this
> is 'standard' behaviour but I would have expected the other way around.

Yes, me too. I think glibc etc first checks the hosts file and then dns.

> > Would you be able to provide a patch to introduce this?
>
> Not yet. I assume we will implement this someway soon, but I really can't
> tell when this will be. I expect that to be in one or two months.

Ok, I might have a go at it earlier, but I'm not sure. Let's see how things
turn out.

Thanks for your reports and research this far anyway!

BTW, future development issues and quirks on this subject should probably be
taken over to the libcurl mailing list instead, where this reply is also
CC'ed.

-- 
 Daniel - been obfuscating curl source code since 1998.
 [[ Do not post private mails to this email address. They won't reach me. ]]
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/