gnugk(1) [debian man page]

GNUGK(1)						    BSD General Commands Manual 						  GNUGK(1)

NAME

     gnugk -- The GNU Gatekeeper

SYNOPSIS

     gnugk [-hdrt] [-c filename] [-s section] [-i IP] [-l n] [-b n] [-u name] [-d name] [-rr] [-o filename] [--pid filename] [--core n]

DESCRIPTION

     The GNU Gatekeeper is an open-source project that implements a H.323 gatekeeper. A H.323 gatekeeper controls all H.323 clients in its zone.
     It allows you, among other things, to register devices, make calls, perform AAA (Authentication, Authorization and Auditing), manage configu-
     rations at runtime and traverse NAT.

OPTIONS

     The behavior of the gatekeeper is determined through command line options and the configuration file. Some command line options may override
     settings found in the configuration file. For example, the option -l overrides the setting "TimeToLive" in the configuration file.  Almost
     every option has a short and a long format, e.g., -c is the same as --config.

     -h --help
	      Show all available options and quit the program.

     -c --config filename
	     Specify the configuration file to use.

     -s --section section
	     Specify which main section to use in the configuration file. The default is [Gatekeeper::Main].

     -i --interface IP
	     Specify the IP address that the gatekeeper listens to. You should leave out this option to let the gatekeeper automatically determine
	     the IP it listens to, unless you want the gatekeeper to bind to a specified IP.

     -l --timetolive n
	     Specify the time-to-live timer (in seconds) for endpoint registration. This overrides the setting "TimeToLive" in the configuration
	     file. A detailed explanation can be found in the manual.

     -b --bandwidth n
	     Specify the total bandwidth available for the gatekeeper. Without specifying this option, bandwidth management is disabled by
	     default.

     --pid filename
	     Specify the pid file.  Only valid for Unix version.

     -u --user name
	     Run the gatekeeper process as this user. Only valid for Unix versions.

     --core n
	     (Unix only) Enable writing core dump files when the application crashes. A core dump file will not exceed n bytes in size. A special
	     constant "unlimited" may also be specified.

   Gatekeeper Mode
     The options in this subsection override the settings in the [RoutedMode] section of the configuration file.

     -d --direct
	     Use direct endpoint call signaling.

     -r --routed
	     Use gatekeeper routed call signaling.

     -rr --h245routed
	     Use gatekeeper routed call signaling and H.245 control channel.

   Debug Information
     -o --output filename
	     Write trace log to the specified file.

     -t --trace
	     Set trace verbosity. The more -t you add, the more verbose to output. For example, use -ttttt to set the trace level to 5.

FILES

     /etc/gatekeeper.ini

AUTHORS

     The project coordinator is Jan Willamowius <jan@willamowius.de>

SEE ALSO

     gatekeeper.ini(5) (and HTML manual)

     http://www.gnugk.org/ (project homepage)

     http://www.gnugk.org/gnugk-manual.html (manual for latest release)

     http://www.willamowius.com/gnugk-support.html (commercial support)

BSD
								  August 7, 2011							       BSD

CRM_MON(8)							  [FIXME: manual]							CRM_MON(8)

NAME

       crm_mon - monitor the cluster's status

SYNOPSIS

	   crm_mon [-V] -d -pfilename -h filename

	   crm_mon [-V] [-1|-n|-r] -h filename

	   crm_mon [-V] [-n|-r] -X filename

	   crm_mon [-V] [-n|-r] -c|-1

	   crm_mon [-V] -i interval

	   crm_mon -?

DESCRIPTION

       The crm_mon command allows you to monitor your cluster's status and configuration. Its output includes the number of nodes, uname, uuid,
       status, the resources configured in your cluster, and the current status of each. The output of crm_mon can be displayed at the console or
       printed into an HTML file. When provided with a cluster configuration file without the status section, crm_mon creates an overview of nodes
       and resources as specified in the file.

OPTIONS

       --help, -?
	   Provide help.

       --verbose, -V
	   Increase the debug output.

       --interval seconds, -i seconds
	   Determine the update frequency. If -i is not specified, the default of 15 seconds is assumed.

       --group-by-node, -n
	   Group resources by node.

       --inactive, -r
	   Display inactive resources.

       --as-console, -c
	   Display the cluster status on the console.

       --one-shot, -1
	   Display the cluster status once on the console then exit (does not use ncurses).

       --as-html filename, -h filename
	   Write the cluster's status to the specified file.

       --daemonize, -d
	   Run in the background as a daemon.

       --pid-file filename, -p filename
	   Specify the daemon's pid file.

       --xml-file filename, -X filename
	   Specify an XML file containing a cluster configuration and create an overview of the cluster's configuration.

EXAMPLES

       Display your cluster's status and get an updated listing every 15 seconds:

	       crm_mon

       Display your cluster's status and get an updated listing after an interval specified by -i. If -i is not given, the default refresh
       interval of 15 seconds is assumed:

	       crm_mon -i interval[s]

       Display your cluster's status on the console:

	       crm_mon -c

       Display your cluster's status on the console just once then exit:

	       crm_mon -1

       Display your cluster's status and group resources by node:

	       crm_mon -n

       Display your cluster's status, group resources by node, and include inactive resources in the list:

	       crm_mon -n -r

       Write your cluster's status to an HTML file:

	       crm_mon -h filename

       Run crm_mon as a daemon in the background, specify the daemon's pid file for easier control of the daemon process, and create HTML output.
       This option allows you to constantly create HTML output that can be easily processed by other monitoring applications:

	       crm_mon -d -p filename -h filename

       Display the cluster configuration laid out in an existing cluster configuration file (filename), group the resources by node, and include
       inactive resources. This command can be used for dry-runs of a cluster configuration before rolling it out to a live cluster.

	       crm_mon -r -n -X filename

FILES

       /var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.

AUTHOR

       crm_mon was written by Andrew Beekhof.

[FIXME: source] 						    07/05/2010								CRM_MON(8)