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

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

NAME

       hobbitlaunch - Master program to launch other Xymon programs

SYNOPSIS

       hobbitlaunch [options]

DESCRIPTION

       hobbitlaunch(8) is the main program that controls the execution and scheduling of all of the components in the Xymon system.

       hobbitlaunch allows the administrator to add, remove or change the set of Xymon applications and extensions without restarting Xymon - hob-
       bitlaunch will automatically notice any changes in the set of tasks, and change the scheduling of activities accordingly.

       hobbitlaunch also allows the administrator to setup specific logfiles for each component of the Xymon system,  instead  of  getting  output
       from all components logged to a single file.

OPTIONS

       --env=FILENAME
	      Loads  the  environment  from  FILENAME  before starting other tools.  The environment defined by FILENAME is the default, it can be
	      overridden by the ENVFILE option in hobbitlaunch.cfg(5)

       --config=FILENAME
	      This option defines the file that hobbitlaunch scans for tasks it must launch. A description of this file is in  hobbitlaunch.cfg(5)
	      The default tasklist is /etc/hobbitlaunch.cfg

       --log=FILENAME
	      Defines the logfile where hobbitlaunch logs information about failures to launch tasks and other data about the operation of hobbit-
	      launch. Logs from individual tasks are defined in the hobbitlaunch.cfg file. By default this is logged to stdout.

       --pidfile=FILENAME
	      Filename which hobbitlaunch saves its own process-ID to. Commonly used by automated start/stop scripts.

       --verbose
	      Logs the launch of all tasks to the logfile. Note that the logfile may become quite large if you enable this.

       --dump Just dump the contents of the hobbitlaunch.cfg file after parsing it.  Used for debugging.

       --debug
	      Enable debugging output while running.

       --no-daemon
	      hobbitlaunch normally detaches from the controlling tty and runs as a background task. This option keeps it  running  in	the  fore-
	      ground.

STARTING TASKS

       hobbitlaunch will read the configuration file and start all of the tasks listed there.

       If a task completes abnormally (i.e. terminated by a signal or with a non-zero exit status), then hobbitlaunch will attempt to restart it 5
       times. If it still will not run, then the task is disabled for 10 minutes. This will be logged to the hobbitlaunch logfile.

       If the configuration file changes, hobbitlaunch will re-read it and notice any changes. If a running task was removed from  the	configura-
       tion, then the task is stopped. If a new task was added, it will be started.  If the command used for a task changed, or it was given a new
       environment definition file, or the logfile was changed, then the task is stopped and restarted with the new definition.

SEE ALSO

       hobbitlaunch.cfg(5), xymon(7)

Xymon							    Version 4.2.3:  4 Feb 2009						   HOBBITLAUNCH(8)
Man Page