A while ago, I upgraded from mon-0.99.3-47 to mon-1.2.0.  I believe that 
was the time when I stopped getting syslog output from mon.

I have this in my mon.cf
syslog_facility = local2

and this in syslog.conf:
local2.debug    /var/log/mon.log


And syslog (redhat linux) running with options "-m 0 -rh".  I've tried 
using 'logger' to test syslog.  And, I've written a small perl script 
that uses some of the openlog/syslog code from mon and it ends up in the 
right place too.

Did something change such that mon is now not syslogging except in case 
of national emergency or something?  What I'm after is some verbose 
logging of failures, alerts, logic, & etc.  I've got some of that by 
enabling historicfile, but I'd much rather something I can log for 
longer times and rotate with syslog.  Plus, that doesn't appear to have 
all the detail I'm after.  Specifically, right now I'm trying to figure 
out why an up-trap submitted via Mon::Client isn't producing an alert. 
My old logging would likely have shown me enough detail.

thanks

Tom Lieuallen
Oregon State University

_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon

Reply via email to