Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

trimhistory(8) [debian man page]

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

NAME

       trimhistory - Remove old Xymon history-log entries

SYNOPSIS

       trimhistory --cutoff=TIME [options]

DESCRIPTION

       The  trimhistory  tool  is  used  to  purge old entries from the Xymon history logs. These logfiles accumulate information about all status
       changes that have occurred for any given service, host, or the entire Xymon system, and is used to generate the event- and history-log web-
       pages.

       Purging	old  entries  can  be done while Xymon is running, since the tool takes care not to commit updates to a file if it changes mid-way
       through the operation. In that case, the update is aborted and the existing logfile is left untouched.

       Optionally, this tool will also remove logfiles from hosts that are no longer defined in the Xymon bb-hosts(5) file. As an extension,  even
       logfiles from services can be removed, if the service no longer has a valid status-report logged in the current Xymon status.

OPTIONS

       --cutoff=TIME
	      This  defines  the  cutoff-time when processing the history logs. Entries dated before this time are discarded. TIME is specified as
	      the number of seconds since the beginning of the Epoch. This is easily generated by the GNU date(1) utility, e.g. the following com-
	      mand will trim history logs of all entries prior to Oct. 1st 2004:

		  trimhistory --cutoff=`date +%s --date="1 Oct 2004"`

       --outdir=DIRECTORY
	      Normally,  files	in  the  BBHIST  directory  are replaced. This option causes trimhistory to save the shortened history logfiles to
	      another directory, so you can verify that the operation works as intended. The output directory must exist.

       --drop Causes trimhistory to delete files from hosts that are not listed in the bb-hosts(5) file.

       --dropsvcs
	      Causes trimhistory to delete files from services that are not currently tracked  by  Xymon.  Normally  these  files  would  be  left
	      untouched if only the host exists.

       --droplogs
	      Process the BBHISTLOGS directory also, and delete status-logs from events prior to the cut-off time. Note that this can dramatically
	      increase the processing time, since there are often lots and lots of files to process.

       --progress[=N]
	      This will cause trimhistory to output a status line for every N history logs or status-log collections it processes, to indicate how
	      far it has progressed. The default setting for N is 100.

       --env=FILENAME
	      Loads the environment from FILENAME before executing trimhistory.

       --debug
	      Enable debugging output.

FILES

       $BBHIST/allevents
	      The eventlog of all events that have happened in Xymon.

       $BBHIST/HOSTNAME
	      The per-host eventlogs.

       $BBHIST/HOSTNAME.SERVICE
	      The per-service eventlogs.

       $BBHISTLOGS/*/*
	      The historical status-logs.

ENVIRONMENT VARIABLES

       BBHIST The directory holding all history logs.

       BBHISTLOGS
	      The top-level directory for the historical status-log collections.

       BBHOSTS
	      The location of the bb-hosts file, holding the list of currently known hosts in Xymon.

SEE ALSO

       xymon(7), bb-hosts(5)

Xymon							    Version 4.2.3:  4 Feb 2009						    TRIMHISTORY(8)

Check Out this Related 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)
Man Page