hobbitd_channel(8) [debian man page]

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

NAME

       hobbitd_channel - Feed a hobbitd channel to a worker module

SYNOPSIS

       hobbitd_channel --channel=CHANNEL [options] workerprogram [worker-options]

DESCRIPTION

       hobbitd_channel	hooks  into  one  of  the  hobbitd(8)  channels  that  provide information about events occurring in the Xymon system.	It
       retrieves messages from the hobbitd daemon, and passes them on to the workerprogram on the STDIN (file descripter 1) of the worker program.
       Worker programs can then handle messages as they like.

       A number of worker programs are shipped with hobbitd, e.g.  hobbitd_filestore(8) hobbitd_history(8) hobbitd_alert(8) hobbitd_rrd(8)

       If you want to write your own worker module, a sample worker module is provided as part of the hobbitd distribution in the hobbitd_sample.c
       file. This illustrates how to easily fetch and parse messages.

OPTIONS

       hobbitd_channel accepts a few options.

       --channel=CHANNELNAME
	      Specifies the channel to receive messages from, only one channel can be used.  This option is required. The following  channels  are
	      available:
	      "status" receives all Xymon status- and summary-messages
	      "stachg" receives information about status changes
	      "page" receives information about statuses triggering alerts
	      "data" receives all Xymon "data" messages
	      "notes" receives all Xymon "notes" messages
	      "enadis" receives information about hosts being disabled or enabled.

       --daemon
	      hobbitd_channel  is normally started by hobbitlaunch(8) as a task defined in the hobbitlaunch.cfg(5) file. If you are not using hob-
	      bitlaunch, then starting hobbitd_channel with this option causes it to run as a stand-alone background task.

       --pidfile=FILENAME
	      If running as a stand-alone daemon, hobbitd_channel will save the proces-ID of the daemon in FILENAME. This is useful for  automated
	      startup- and shutdown- scripts.

       --env=FILENAME
	      Loads  the  environment variables defined in FILENAME before starting hobbitd_channel.  This is normally used only when running as a
	      stand-alone daemon; if hobbitd_channel is started by hobbitlaunch, then the environment is controlled by the task definition in  the
	      hobbitlaunch.cfg(5) file.

       --log=FILENAME
	      Redirect output to this log-file.

       --debug
	      Enable debugging output.

FILES

       This program does not use any configuration files.

SEE ALSO

       hobbitd(8), xymon(7)

Xymon							    Version 4.2.3:  4 Feb 2009						HOBBITD_CHANNEL(8)

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)