Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!rice!sun-spots-request From: mrapple@quack.sac.ca.us (Nick Sayer) Newsgroups: comp.sys.sun Subject: Re: syslog.conf and `LOGHOST' Keywords: Miscellaneous Message-ID: <1990Oct7.223111.27239@rice.edu> Date: 7 Oct 90 21:30:00 GMT Sender: sun-spots-request@rice.edu Organization: Sun-Spots Lines: 37 Approved: Sun-Spots@rice.edu Originator: spots@walhalla.rice.edu X-Sun-Spots-Digest: Volume 9, Issue 321, message 11 X-Refs: Original: v9n304 glenn@csri.toronto.edu (Glenn Mackintosh) writes: >schoch@trident.arc.nasa.gov (Steve Schoch) writes: >>My question is: "How does syslogd find out whether the current host is >>the loghost or not?" It doesn't seem to work on our system. Does it use >>gethostbyname()? I have modified libc.so to use the nameserver instead of >>the host table. >Since you are using the nameserver you are going to need an A record for >"loghost" in the nameserver data. I.e. something of the form: >loghost IN A ???.???.???.??? Perhaps a better idea would be to add loghost as an alternate name to your host name in /etc/hosts -- and therefore in the yellow pages. Having it in the name server means everyone knows about it, and they don't need to. You should also probably have a mailhost entry, depending on your setup. Our /etc/hosts: localhost 127.0.0.1 uop 138.9.200.1 loghost mailhost zeus 138.9.200.2 So the yellow pages can tell you who is the mailhost and loghost, but nobody else really needs to know. Also, there is a bug in older syslogs that keep them from working in this regard. The fix is to simply define LOGHOST near the begining of the file on your loghost machine. Kinda defeats the purpose. SunOS 4.1 does not have this bug. SunOS 4.0 does. I don't know where in between it got fixed. Nick Sayer | Disclaimer: N6QQQ [44.2.1.17 soon] | "Just because you're reading my post doesn't mrapple@quack.sac.ca.us | mean we're gonna take long showers together." 209-952-5347 (Telebit) | -- Gunnery Sgt. Thomas Highway