On Thu, Dec 13, 2007 at 03:20:07PM -0500, 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.
Devil's advocate: but why should they? If I have a loghost or if I will have one, then I don't want localhost to be aliased as loghost. /etc/syslog.conf already deals with loghost being defined or not. So why not just remove the warning instead? Another issue is that one might like secure syslogging, including secure discovery and authentication of loghosts. I think Secure By Default provides the best rationale to do something about this. So why not this instead: - add a property to svc:/system/system-log to toggle whether insecure lookup of loghost and logging to loghost is allowed, default to no Nico -- _______________________________________________ networking-discuss mailing list [email protected]
