KUMO-MANAGER(1) General Commands Manual KUMO-MANAGER(1)NAME
kumo-manager - kumofs manager daemon
SYNOPSIS
kumo-manager -l <addr[:port=19700]> -p <addr[:port=19700]>
DESCRIPTION
kumo-manager manages kumo-servers. Run this daemon on one or two hosts. You can get live status of the kumo-manager using kumoctl command.
OPTIONS -p <addr[:port=19700]> --partner
master-slave replication partner
-a --auto-replace
enable auto replacing
-Rs <number=4> --replace-delay
delay time of auto replacing in sec.
-k <number=2> --keepalive-interval
keepalive interval in seconds
-Ys <number=1> --connect-timeout
connect timeout time in seconds
-Yn <number=4> --connect-retry-limit
connect retry limit
-Ci <number=2> --clock-interval
clock interval in seconds
-TW <number=2> --write-threads
number of threads for asynchronous writing
-TR <number=4> --read-threads
number of threads for asynchronous reading
-o <path.log> --log
output logs to the file
-g <path.mpac> --binary-log
enable binary log
-v --verbose
-d <path.pid> --daemon
AUTO REPLACING
See kumoctl(1) for details.
EXAMPLE
[on mgr1 ]$ kumo-manager -v -l mgr1 -p mgr2 -o -
[on mgr2 ]$ kumo-manager -v -l mgr2 -p mgr1 -g errlog.mpac
[localhost]$ kumo-manager -v -l localhost -Ys 4 -Yn 2
SEE ALSO kumoctl(1), kumolog(1).
kumo-manager July 2009 KUMO-MANAGER(1)
Check Out this Related Man Page
prelude-manager(1) General Commands Manual prelude-manager(1)NAME
prelude-manager - Collects and normalize events.
SYNOPSIS
prelude-manager [options]
DESCRIPTION
Prelude Manager is a high-availability server which can collect, filter, relay, reverse-relay, normalize and store events. Events can come
from registered analyzers and/or managers. The common usage is to store nomalized events into a database, thus this can be extended to
store informations in plain text or xml files.
OPTIONS
Some prelude-manager option are contextual, they have to be prefixed by another.
--prelude Prelude generic options
--profile=<name> Profile to use for this analyzer
--heartbeat-interval=<interval> Number of seconds between two heartbeat
--server-addr=<address> Address where this sensor should report to (addr:port)
--analyzer-name=<name> Name for this analyzer
--db=<INAME>
Options for the libpreludedb plugin
-t, --type=<type> Type of database (mysql/pgsql/sqlite3)
-l, --log=<file name> Log all queries in a file, should be only used for debugging purpose
-h, --host=<address> The host where the database server is running (in case of client/server database)
-f, --file=<file name> The file where the database is stored (in case of file based database)
-p, --port=<port number> The port where the database server is listening (in case of client/server database)
-d, --name=<name> The name of the database where the alerts will be stored
-u, --user=<user> User of the database (in case of client/server database)
-P, --pass=<password> Password for the user (in case of client/server database)
--debug=<INAME>
Option for the debug plugin
-o, --object=<name> Name of IDMEF object to print (no object provided will print the entire message)
-l, --logfile=<file name> Specify output file to use (default to stdout)
--relaying=<INAME>
Relaying plugin option
-p, --parent-managers=<address> List of managers address:port pair where messages should be sent to
--textmod=<INAME>
Option for the textmod plugin
-l, --logfile=<file name> Specify logfile to use
--xmlmod=<INAME>
Option for the xmlmod plugin
-l, --logfile=<file name> Specify output file to use
-v, --validate=<xml> Validate IDMEF XML output against DTD
-f, --format=<format> Format XML output so that it is readable
-d, --disable-buffering=<boolean> Disable output file buffering to prevent truncated tags
--idmef-criteria-filter=<INAME> Filter message based on IDMEF criteria
-r, --rule=<rule> Filter rule, or filename containing rule
--hook=<value> Where the filter should be hooked (reporting|reverse-relaying|plugin name)
--config=<file name>
Configuration file to use
-v, --version
Print version number
-D, --debug-level=<level>
Run in debug mode
-d, --daemon
Run in daemon mode
-P, --pidfile=<file name>
Write Prelude PID to pidfile
-c, --child-managers=<address>
List of managers address:port pair where messages should be gathered from
-l, --listen=<address>
Address the sensors server should listen on (addr:port)
-f, --failover=<boolean>
Enable failover for specified report plugin
-h, --help
Print help
FILES
/etc/prelude/prelude-manager.conf - the configuration file
BUGS
This man page hadn't been proof-read yet.
SEE ALSO prelude-adduser(1)prelude-manager(1)