Thanks for the quick replies. Looks like my system is running fine.
I found the expected messages in the syslog.dated files.
Here are some helpful tips from the replies I received.
- It's perfectly possible not to have new messages for months
- Verify that syslogd has the messages file open: "fuser -v
/var/adm/messages"
- Look in the /var/adm/syslog.dated directory and see if it has a
subdirectory for today's date
- In /etc/syslog.conf, only kern.debug goes to /var/adm/messages.
Everything else goes to /var/adm/syslog.dated log
- Test by logging a message: /usr/bin/logger -p kern.debug "Testing. 1. 2.
3."
[By the way --> this shows up in User.log for some reason; not messages]
- See man logger for details on its usage. It's handy.
- /var's free size is maybe too small, which would cause syslogd stop
logging
-----Original Message-----
Tru64 Managers,
On our Tru64 5.1 system, the "messages" file (/var/adm/messages) seems to be
too quiet. The last message logged is from August 10th.
I checked that syslogd is running.
Is syslogd the only process that writes to /var/adm/messages? I'm a little
concerned that there have been no recent entries. But-- maybe things are
just running perfectly and there are no events to write to 'messages'.
Thanks,
Robert Aldridge
Alliance, Ohio
Received on Thu Oct 18 2001 - 14:45:45 NZDT