James Carlson wrote: > W. Wayne Liauh writes: > >> I was playing with my dhcp client and when I rebooted, I saw the following >> message: >> >> " unknown syslogd: line 24: WARNING: loghost could not be resolved " >> >> What could have I done wrong? Any suggestions to remove this problem? >> Apologize for the terse info I am providing. >> > > This is CR 4351417, an ancient problem. The system scripts just don't > populate the loghost entry. > > To work around it, you can add "loghost" to the localhost line in > /etc/hosts. >
IMHO, this is somewhat backwards. Or at least the "amiloghost()" logic is. I'd argue that amiloghost() should return "true" if there is no mapping for loghost/syslog found in the name service table, not just if it can bind loghost/syslog locally. Darren _______________________________________________ networking-discuss mailing list [email protected]
