Leslie --
My experience is with syslog configuration under Solaris,
rather than AIX, but I'm hoping this might help....
It might be that syslogd needs for the file specified in
syslog.conf to exist, so that it can write to it. I've found that
when I execute `kill -HUP <syslog_pid>` to reload syslog.conf
under Solaris, syslogd doesn't complain about a missing file,
but syslogd doesn't create the log file either. After creating the file,
you have to reload syslog.conf again before syslogd will begin
logging to the file.
Also, the syslog.conf file requires tabs as the field
delimiter. If you highlight with the mouse, then copy & paste a
syslog,conf entry, the tabs will get converted to spaces and
you won't get the results you expect. I've also had the case
where there was an extra, hard-to-notice, space before or after
one of the fields.
Hope this helps,
Elizabeth
http://hometown.aol.com/ebagley2/career
In a message dated 1/13/00 10:50:44 PM Central Standard Time,
lclark@US.IBM.COM writes:
> I'm stuck, and I'm sure someone out there knows what I'm doing wrong.
> If not, I'll call AIX support and ask the dumb question.
>
> There is an 4.1 system with old netview & ciscoworks on it. It got a new
> address and I used the old address on a brand new box, AIX 4.3.2, latest
> recommended maintenance. Routers were logging to the old box. Now
> they should log to the new box using the syslog facility. I added the
> record
> 'local7.info /var/log/nmslog' to syslog.conf and did a refresh -s
> syslogd.
> The directory exists (I created it), but nothing is showing up. Is there
> something
> else I had to do? No one here remembers how they got it working on the old
> box
> but I believe it was actually set up by the install of Ciscoworks V3.
>
> Suggestions welcome...
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Detroit
|