Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hobbitlaunch(8) [debian 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)

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