Re: syslogd and 2.1.14

Keith Rohrer (rohrer@obey.reply-to.line)
Sun, 8 Dec 1996 12:41:39 -0600 (CST)

> > syslogd prior to 1.3.1 gets segv on a NULL pointer after gethostbyname if
> > the hostname cannot be resolved. Sounds like your nameserver is not
> > resolving the hostname.
> It should be.. I got the version of syslogd that came w/ slack 96.. But,
> syslogd is loading when my linux box boots when it says Staring Daemons..
> And i am *not* connected to the internet.. So why would it use my
> nameserver??
Dunno. Actually, anything recent that does gethostbyname (linking to doesn't grok "localhost" in /etc/hosts. I don't know
the exact problem, but it seems to go to the nameserver (despite the
proper "order hosts, bind" in /etc/resolv.conf) and eventually comes
up with (now that I've kludged things) when it
resolves the name localhost. Without my kludge, localhost doesn't
get resolved at all unless my internet connection is up, in which
case it comes out as Is this the way it's
supposed to be? I'd like to think ' localhost' in /etc/hosts
would suppress all nameserver access asking about 'localhost', but
apparently not so...