PageRenderTime 136ms CodeModel.GetById 127ms app.highlight 1ms RepoModel.GetById 7ms app.codeStats 0ms

/hobbit/client-local.cfg

http://github.com/brinkman83/bashrc
Config | 125 lines | 104 code | 21 blank | 0 comment | 0 complexity | 4f169f31b5fe72c1064ec11196fb1964 MD5 | raw file
  1# The client-local.cfg file contains configuration for
  2# the Xymon clients running on monitored systems. When
  3# clients contact the Xymon server, they get the section
  4# from this file which matches their hostname or operating
  5# system.
  6#
  7# The following configuration items are currently possible:
  8#   "log:FILENAME:MAXDATA"
  9#       Monitor the text-based logfile FILENAME, and report
 10#       back at most MAXDATA bytes. The Xymon client will
 11#       only report back entries generated during the past
 12#       30 minutes, so MAXDATA is an upper limit.
 13#   "ignore EXPRESSION"
 14#       Must follow a "log:..." entry. Lines matching the 
 15#       regular EXPRESSION are not sent to the Xymon server.
 16#   "trigger EXPRESSION"
 17#       Must follow a "log:..." entry. Lines matching the
 18#       regular EXPRESSION are always sent to the Xymon server.
 19#       Use this for extremely critical errors that must be
 20#       reported.
 21#
 22#   "linecount:FILENAME"
 23#       Monitor the text-based logfile FILENAME, but just
 24#       count the number of times certain expressions appear.
 25#       This processes the entire file every time. It must
 26#       be followed by one or more lines with
 27#   "KEYWORD PATTERN"
 28#       KEYWORD identifies this count. You can use any string
 29#       except whitespace. PATTERN is a regular expression
 30#       that you want to search for in the file.
 31#
 32#   "file:FILENAME[:hash]"
 33#       Monitor the file FILENAME by reporting file metadata.
 34#       The Xymon client will report back all of the file 
 35#       meta-data, e.g. size, timestamp, filetype, permissions
 36#       etc. The optional "hash" setting is "md5", "sha1" or
 37#       "rmd160", and causes the Xymon client to compute a
 38#       file hash using the MD5, SHA-1 or RMD160 algorithm.
 39#       Note: Computing the hash value may be CPU-intensive,
 40#             so You should use this sparingly. For large-scale
 41#             file integrity monitoring, use a real host-based
 42#             IDS (Tripwire, AIDE or similar).
 43#
 44#   "dir:DIRECTORY"
 45#       Monitor the size of DIRECTORY, including sub-directories.
 46#       This causes the Xymon client to run a "du" on DIRECTORY
 47#       and send this back to the Xymon server.
 48#       Note: Running "du" on large/deep directory structures can
 49#             cause a significant system load.
 50#
 51# NB: If FILENAME and/or DIRECTORY are of the form `COMMAND`,
 52#     then COMMAND is run on the client, and the lines output
 53#     by the command are used as the file- or directory-names.
 54#     This allows you to monitor files where the names change,
 55#     as long as you can script some way of determining the
 56#     interesting filenames.
 57
 58[sunos]
 59log:/var/adm/messages:10240
 60
 61[osf1]
 62log:/var/adm/messages:10240
 63
 64[aix]
 65log:/var/adm/syslog/syslog.log:10240
 66
 67[hp-ux]
 68log:/var/adm/syslog/syslog.log:10240
 69
 70[win32]
 71
 72[freebsd]
 73log:/var/log/messages:10240
 74
 75[netbsd]
 76log:/var/log/messages:10240
 77
 78[openbsd]
 79log:/var/log/messages:10240
 80
 81[linux]
 82log:/var/log/messages:10240
 83ignore MARK
 84
 85[linux22]
 86log:/var/log/messages:10240
 87ignore MARK
 88
 89[redhat]
 90log:/var/log/messages:10240
 91ignore MARK
 92
 93[debian]
 94log:/var/log/messages:10240
 95ignore MARK
 96
 97[suse]
 98log:/var/log/messages:10240
 99ignore MARK
100
101[mandrake]
102log:/var/log/messages:10240
103ignore MARK
104
105[redhatAS]
106log:/var/log/messages:10240
107ignore MARK
108
109[redhatES]
110log:/var/log/messages:10240
111ignore MARK
112
113[rhel3]
114log:/var/log/messages:10240
115ignore MARK
116
117[irix]
118log:/var/adm/SYSLOG:10240
119
120[darwin]
121log:/var/log/system.log:10240
122
123[sco_sv]
124log:/var/adm/syslog:10240
125