Server OS X 10.1.x (and 10.2.x) runs daily cron jobs to rotate system.log and other logs. I think the same thing happens on the client version of Mac OS X.
It appears that after that cron job runs servers that have webmin installed have very few entries put into the system.log from then on. Other logs appear not to be affected.
This is not a matter of looking somehow at the wrong file - it's the right file and all the entries that are present are viewable. Nor does this appear to be some problem with priveleges - as far as I can tell they are ok.
It's more like various services that should report to the system.log can't.
Here's an example of the syslog.conf - <quote>
*.err;kern.*;auth.notice;authpriv,remoteauth.none;mail.crit /dev/console
*.notice;*.info;authpriv,remoteauth,ftp.none;kern.debug;mail.crit /var/log/system.log
# The authpriv log file should be restricted access; these
# messages shouldn't go to terminals or publically-readable
# files.
authpriv.*;remoteauth.crit /var/log/secure.log
lpr.info /var/log/lpr.log
mail.* /var/log/mail.log
ftp.* /var/log/ftp.log
netinfo.err /var/log/netinfo.log
*.emerg *
<end quote>
Logged In: YES
user_id=129364
Did you actually use Webmin's System Logs module to edit the
logging configuration? If not, I can't see how it would be
related ..
Logged In: NO
> Did you actually use Webmin's System Logs module to edit the
logging configuration? If not, I can't see how it would be
related ..
I'm not sure either. But i've tried with and without using the webmin controls to set the system.log.