> it does seem to be functioning fine , I got an email to my outlook from this system this morning with backup log details , so mail does seem to be working , even though it says the last entry was on August 13 , Im still a bit confused to be honest , which file is it actually writing to now Im wondering ?
Always test syslogd with logger as mentioned above. These two commands will put an entry at the end of the two logs (assuming you have a standard syslog.conf file):
logger "testing syslog.log"
logger -p mail.info "testing mail.log"
If nothing shows up, then syslogd is not running or not writing to the current syslog.log and mail.log files. Stop and restart syslogd and repeat the logger test. If logger still does not write anything new, then list the syslog.conf file using cat -t:
cat -t /etc/syslog.conf
mail.debug^I^I/var/adm/syslog/mail.log
*.info;mail.none;local5.none;auth.none^I/var/adm/syslog/syslog.log
auth.info^I^I/var/adm/syslog/auth.log
local5.info^I^I/var/adm/syslog/ftpd.log
*.alert^I^I^I/dev/console
*.alert^I^I^Iroot
*.emerg^I^I^I*
There must be *NO* spaces anywhere in the file. The ^I symbol is the TAB character but in vi, it looks like spaces. This space character restriction has always existed for syslogd.
Bill Hassell, sysadmin
