logfetch(1) [debian man page]

LOGFETCH(1)						      General Commands Manual						       LOGFETCH(1)

NAME

       logfetch - Xymon client data collector

SYNOPSIS

       logfetch CONFIGFILE STATUSFILE

DESCRIPTION

       logfetch  is part of the Xymon client. It is responsible for collecting data from logfiles, and other file-related data, which is then sent
       to the Xymon server for analysis.

       logfetch uses a configuration file, which is automatically retrieved from the Xymon server. There is no	configuration  done  locally.  The
       configuration  file is usually stored in the $BBHOME/tmp/logfetch.cfg file, but editing this file has no effect since it is re-written with
       data from the Xymon server each time the client runs.

       logfetch stores information about what parts of the monitored logfiles have been processed already in the $BBHOME/tmp/logfetch.status file.
       This file is an internal file used by logfetch, and should not be edited. If deleted, it will be re-created automatically.

SECURITY

       logfetch  needs	read access to the logfiles it should monitor. If you configure monitoring of files or directories through the "file:" and
       "dir:" entries in client-local.cfg(5) then logfetch will require at least read-acces to the directory where the file  is  located.  If  you
       request checksum calculation for a file, then it must be readable by the Xymon client user.

       Do  NOT	install  logfetch  as  suid-root. There is no way that logfetch can check whether the configuration file it uses has been tampered
       with, so installing logfetch with suid-root privileges could allow an attacker to read any file on the system by using a hand-crafted  con-
       figuration file. In fact, logfetch will attempt to remove its own suid-root setup if it detects that it has been installed suid-root.

ENVIRONMENT VARIABLES

       DU     Command  used  to collect information about the size of directories.  By default, this is the command du -k. If the local du-command
	      on the client does not recognize the "-k" option, you should set the DU environment  variable  in  the  $BBHOME/etc/hobbitclient.cfg
	      file to a command that does report directory sizes in kilobytes.

FILES

       $BBHOME/tmp/logfetch.cfg

       $BBHOME/tmp/logfetch.status

SEE ALSO

       xymon(7), hobbit-clients.cfg(5)

Xymon							    Version 4.2.3:  4 Feb 2009						       LOGFETCH(1)

MSGCACHE(8)						      System Manager's Manual						       MSGCACHE(8)

NAME

       msgcache - Cache client messages for later pickup by hobbitfetch

SYNOPSIS

       msgcache [options]

DESCRIPTION

       msgcache  implements  a Xymon message cache. It is intended for use with clients which cannot deliver their data to the Xymon server in the
       normal way. Instead of having the client tools connect to the Xymon server, msgcache runs locally and the client tools then  deliver  their
       data to the msgcache daemon. The msgcache daemon is then polled regularly by the hobbitfetch(8) utility, which collects the client messages
       stored by msgcache and forwards them to the Xymon server.

       NOTE: When using msgcache, the BBDISP setting for the clients should be BBDISP=127.0.0.1 instead of pointing at the real Xymon server.

RESTRICTIONS

       Clients delivering their data to msgcache instead of the real Xymon server will in general not notice this. Specifically, the  client  con-
       figuration  data provided by the Xymon server when a client delivers its data is forwarded through the hobbitfetch / msgcache chain, so the
       normal centralized client configuration works.

       However, other commands which rely on clients communicating directly with the Xymon server will not work.  This	includes  the  config  and
       query commands which clients may use to fetch configuration files and query the Xymon server for a current status.

       The download command also does not work with msgcache.  This means that the automatic client update facility will not work for clients com-
       municating via msgcache.

OPTIONS

       --listen=IPADDRESS[:PORT]
	      Defines the IP-address and portnumber where msgcache listens for incoming connections. By default, msgcache listens for  connections
	      on all network interfaces, port 1984.

       --server=IPADDRESS[,IPADDRESS]
	      Restricts  which servers are allowed to pick up the cached messages.  By default anyone can contact the msgcache utility and request
	      all of the cached messages. This option allows only the listed servers to request the cached messages.

       --max-age=N
	      Defines how long cached messages are kept. If the message has not been picked up with N seconds after being delivered  to  msgcache,
	      it is silently discarded. Default: N=600 seconds (10 minutes).

       --daemon
	      Run as a daemon, i.e. msgcache will detach from the terminal and run as a background task

       --no-daemon
	      Run  as  a  foreground task. This option must be used when msgcache is started by hobbitlaunch(8) which is the normal way of running
	      msgcache.

       --pidfile=FILENAME
	      Store the process ID of the msgcache task in FILENAME.

       --logfile=FILENAME
	      Log msgcache output to FILENAME.

       --debug
	      Enable debugging output.

SEE ALSO

       hobbitfetch(8), xymon(7)

Xymon							    Version 4.2.3:  4 Feb 2009						       MSGCACHE(8)