SGI Techpubs Library

Linux  »  Man Pages
find in page



NAME
       eventmond - Event Manager

SYNOPSIS
       eventmond [-B-] [-W] [-p <PortNumber>] [-s <SocketFileName>]
               [-c <SubscribersFileName] [-D <DebugInitString>]
               [-O <OutputFileName>]

       eventmond -L | -U | -Q | -S | -I | -C | -M <TaskName> [-P <Parameters>]

       eventmond -T [A | I]

       eventmond -h

DESCRIPTION
       eventmond is a multi-threaded UNIX process that runs at system startup,
       collecting events from producer applications and sending events to con-
       sumer  applications for processing. eventmond also provides a framework
       for loading plugins (called Tasks) that perform event  related  activi-
       ties.  Each  Task  runs as an independent thread.  Tasks can be loaded,
       unloaded, started, stopped, etc. ESP takes advantage  of  this  feature
       with  its ESP consumer application (espdso) and its general purpose log
       monitor (logmon).

       By default, eventmond monitors TCP/IP  port  5553  (user  configurable)
       waiting  for connections from client applications to perform one of the
       following functions:

       o Register a subscription for events  from  a  particular  application.
         Events  are  subscribed  for  by application name and event class and
         type values.

       o Log an event that consumer applications have subscribed for

       o Send a command to eventmond or to a loaded Task

       eventmond uses a producer/consumer architecture. Applications that cre-
       ate  events and send them to eventmond are called producer applications
       (producers). Applications that subscribe for events are called consumer
       applications  (consumers). Producers and consumers can communicate with
       the instance of eventmond running on the local system, or they can send
       subscription requests and events to an instance of eventmond running on
       a remote system.

       eventmond does not perform any processing or handling  of  event  data.
       It's  job  is  to make sure logged events get delivered to the consumer
       applications that have subscribed for them. Producer  applications  log
       events  to  eventmond  via  the  Event Manager API or the emgrlogger(1)
       utility (or the esplogger(1) utility if they  are  ESP  events).   Con-
       sumers  use the same facilities when registering subscription requests.

       Each producer application has control over its  event  class  and  type
       definitions.  Consumer applications subscribe for specific events based
       on producer name (appname), class, type, and/or by regular  expression.
       Events can be subscribed for by local and remote consumers.

OPTIONS
       Various  command  line  options have been separated into various group-
       ings.  General purpose options are followed by event  manager  releated
       options and Task related options.

       -h      Print "help" information and exit.

   EVENT MANAGER RELATED OPTIONS
       The  following command line options can be used when using eventmond to
       monitor and manage events.

       -s <SocketFileName>
               Set the eventmond command interface socket file name  to  some-
               thing other than the default value (/tmp/s.eventmond).

       -p <PortNumber>
               Set  the  emgrAPI  incoming port number to something other than
               the default value (5553).

       -W      Start eventmond up in watchdog mode. When running  in  watchdog
               mode,  there  will be two eventmond processes running. One per-
               forms event and task management functions and  one  acts  as  a
               watchdog, restarting eventmond should a problem occur.

       -c <SubscribersFileName>
               Set file where subscribers information will be stored.

       -B-     Start eventmond up in inter-active mode and not in daemon mode.

       -D <DebugInitString>
               Provide a string containing debug tags and levels for the moni-
               toring of eventmond functionality and behavior.

       -O <OutputFile>
               Specify  an  output  file  where  debug  messages  will be sent
               (instead of the console).

   TASK RELATED OPTIONS
       The following command line options can be used when invoking  eventmond
       to perform Task related functions.

       -L      Load a Task and start it running.

       -U      Stop a Task from running and then Unload it.

       -Q      Stop a Task from running.

       -S      Start a Task that was already loaded.

       -I      Display Task specific information.

       -C      Send a command to a Task.

       -M      Send a message to a Task.

       -P <Parameters>
               Used  in  conjunction  with  -L, -U, -Q, -S, -I, and -C command
               line options to specify Task specific parameters.

       -T      Display a list of all Tasks currently loaded and indicate their
               status.   To display a list of all active Tasks, include "A" on
               the command line. To display a  list  of  all  inactive  Tasks,
               include "I" on the command line.

SEE ALSO
       espnotify(1), esplogger(1), emgrlogger(1), chkconfig (8), esp(8)

REFERENCES
       SGI Embedded Support Partner User Guide

                                                                  EVENTMOND(8)

Output converted with man2html


home/search | what's new | help