Commit c6622761 authored by thomas.forbriger's avatar thomas.forbriger Committed by thomas.forbriger
Browse files

report possible message criticality levels in online help

This is a legacy commit from before 2015-05-18.
It may be incomplete as well as inconsistent.
See COPYING.legacy and README.history for details.


SVN Path:     http://gpitrsvn.gpi.uni-karlsruhe.de/repos/TFSoftware/trunk
SVN Revision: 4708
SVN UUID:     67feda4a-a26e-11df-9d6e-31afc202ad0c
parent 42d27f2e
......@@ -35,6 +35,8 @@
# 05/01/2012 V0.1 Daniel Armbruster
# 12/01/2012 V0.2 provide nagios status line
# 10/05/2012 V0.3 provide output to stdout
# 18/05/2012 V0.4 provide information regarding possible message
# criticalities (thof)
#
# =============================================================================
"""
......@@ -52,7 +54,7 @@ import csbacklog
from email.mime.text import MIMEText
from collections import deque
__version__ = "V0.3"
__version__ = "V0.4"
__subversion__ = "$Id$"
__license__ = "GPLv2"
__author__ = "Daniel Armbruster"
......@@ -122,6 +124,16 @@ def help():
-o|--out Send output to stdout instead of sending an email.
PATH Path(s) of the logfile(s) to check. If not specified the
logfiles in /var/log/ were investigated.
-------------------------------------------------------------------------------
csback distibuishes foru different levels of message criticality:
INFO: indicates normal operation
WARNING: indicates any problems which were expected and are tolerated
CRITICAL: indicates a checksum mismatch
ERROR: indicates errors (missing files, etc)
For INFO and WARNING the ten most recent messages are reported. For CRITICAL
and ERROR all messages currently present in the log file are reported.
The nagios report is "CSBACK OK" if no messages of levels WARNING, CRITICAL,
or ERROR are present.
"""
sys.stdout.write(help_text)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment