Re: Failure to find designatated monitor reported as untested
On Wed, 15 Jun 2011, Nico Kadel-Garcia wrote: I believe you, but wasn't seeing them in syslog, even with -d in the command line. If I can talk you, as the original author, to enhance your perl, to report a missing status rather than merely untested, I'd appreciate that quite a lot. i just checked in changes to the trunk for module mon and mon-client which added a configerr state. there are changes to clients/monshow and clients/mon.cgi which should reflect this. i tested it a bit and it seems to work, so it'd be nice if you could check out the code and confirm for yourself that it works. it may take some amount of time before the read-only public cvs repo is synced with the devel repo at sf. these are the revisions: cvs ci -m added configerr state cvs commit: Examining . cvs commit: Examining alert.d cvs commit: Examining cgi-bin cvs commit: Examining clients cvs commit: Examining clients/skymon cvs commit: Examining doc cvs commit: Examining etc cvs commit: Examining mon.d cvs commit: Examining muxpect cvs commit: Examining state.d cvs commit: Examining utils Checking in mon; /cvsroot/mon/mon/mon,v -- mon new revision: 1.27; previous revision: 1.26 done Mailing mon-com...@lists.sourceforge.net... Generating notification message... Generating notification message... done. Checking in clients/mon.cgi; /cvsroot/mon/mon/clients/mon.cgi,v -- mon.cgi new revision: 1.6; previous revision: 1.5 done Checking in clients/monshow; /cvsroot/mon/mon/clients/monshow,v -- monshow new revision: 1.4; previous revision: 1.3 done Mailing mon-com...@lists.sourceforge.net... Generating notification message... Generating notification message... done. Checking in doc/mon.8; /cvsroot/mon/mon/doc/mon.8,v -- mon.8 new revision: 1.8; previous revision: 1.7 done Mailing mon-com...@lists.sourceforge.net... Generating notification message... Generating notification message... done. cvs ci -m added configerr state cvs commit: Examining . cvs commit: Examining Mon Checking in Mon/Client.pm; /cvsroot/mon/mon-client/Mon/Client.pm,v -- Client.pm new revision: 1.4; previous revision: 1.3 done Mailing mon-com...@lists.sourceforge.net... Generating notification message... Generating notification message... done. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Failure to find designatated monitor reported as untested
On Tue, Jun 14, 2011 at 10:34 PM, Jim Trocki troc...@gmail.com wrote: On Tue, 14 Jun 2011, Nico Kadel-Garcia wrote: Not being executable, I think, should be the test, rather than merely not being present. well, both are tested and if problems are found, reported to syslog. other related troubles are reported as well. I believe you, but wasn't seeing them in syslog, even with -d in the command line. I see a check for the existence of the directory and its report to syslog, but not for the absence of a particular monitor tool, or even if I yank the /usr/local/lib/mon/mon.d directory.. I'm not sure why. Looks like I'd like to review the settings for rsyslog, used on Debian, but due to typical system security, it's often awkward for a non-root user to parse through these logs. If I can talk you, as the original author, to enhance your perl, to report a missing status rather than merely untested, I'd appreciate that quite a lot. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Failure to find designatated monitor reported as untested
On Tue, 14 Jun 2011, Nico Kadel-Garcia wrote: Not being executable, I think, should be the test, rather than merely not being present. well, both are tested and if problems are found, reported to syslog. other related troubles are reported as well. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
