On Thu, Feb 01, 2001 at 09:27:49AM +1100, [EMAIL PROTECTED] wrote:

> and the strace showed that the slow host *does* read the file
> /etc/host.conf first - it just doesn't seem to find the information it
> wants there!  (Since the NIS stuff starts, afterwards.)

If you aren't using nis, you may as well delete all references to it 
from nsswitch.conf.

192.168.1.1     posh.localdomain        posh
127.0.0.1       localhost.localdomain   localhost       posh

For no valid reason, other than it looks different to my /etc/hosts,
I'd try making that look like:

127.0.0.1       localhost
192.168.1.1     posh.localdomain        posh

when you send traffic to a local interface, you are actually sending
traffic to the local loop interface. You can check for yourself by 
doing an ifconfig and then ping -c5  192.168.1.1, then do another 
ifconfig and compare RX and TX packets on eth0 and lo.

If you aren't running a name server, try moving /etc/resolv.conf
out of the way.

> If I want to modify the source to do some printf()s to trace what's
> happening for the reading of the host.conf file - what library should I
> be modifying?  What provides the functionality for reading host.conf?

libresolv.so.2 ?

grep -l /etc/hosts /lib/*
Basically you want libc6 sources.
(Do you really want to hack libc6?)

Theres also a ltrace command that traces library calls.

Do you have the same version libc6 package installed on both boxes?
rpm -qa (from memory) on both boxes and diff them.

Basically, I have no idea what the problem is :)

-- 
        chesty


-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug

Reply via email to