Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

Check Out this Related Man Page

globus_gram_job_manager_configuration(3)		      globus gram job manager			  globus_gram_job_manager_configuration(3)

NAME
globus_gram_job_manager_configuration - Job Manager Configuration The Job Manager is generally configured using the setup-globus-gram-job- manager setup script. This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file $GLOBUS_LOCATION/etc/globus-job-manager.conf. Configuration File Options -k Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential. -home GLOBUS_LOCATION Set the GLOBUS_LOCATION environment variable to the specified Globus-Location. -target-globus-location GLOBUS_LOCATION Set the GLOBUS_LOCATION environment variable to the execution node's GLOBUS_LOCATION, if different than the GRAM node's GLOBUS_LOCATION -type JOB_MANAGER_TYPE Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is needed. -history PATH Set the path to the directory to store job history files. -cache-location PATH Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available RSL substitutions. -extra-envvars VAR1[=VAL],VAR2,... The Job manager will attempt to get the listed VARs from its environment and set them the same for the job's environment. For example, -extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE -scratch-dir-base PATH Set the default scratch directory root for the job manager. Job-specific scratch directories will be created as a subdirectory of this directory. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available RSL substitutions. If this option is not present in the configuration file, then the job manager will create scratch directories as subdirectories of the user's home directory. -condor-arch ARCH Set the condor architecture for this job manager to be the specified ARCH. This is optional when the job manager type is condor. -condor-os OSNAME Set the condor operating system name for this job manager to be the specified OSNAME. This is optional when the job manager type is condor. -globus-gatekeeper-host HOST Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution. -globus-gatekeeper-port PORT Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution. -globus-gatekeeper-subject SUBJECT Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution. -globus-host-manufacturer MANUFACTURER Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution. -globus-host-cputype CPUTYPE Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution. -globus-host-osname OSNAME Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution. -globus-host-osversion OSVERSION Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution. -globus-tcp-port-range RANGE Set the range of TCP port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_PORT_RANGE environment variable and RSL substitution. -globus-tcp-source-range RANGE Set the range of TCP source port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_SOURCE_RANGE environment variable and RSL substitution. -state-file-dir PATH Set the path to store job manager state files (used for restarting a job manager which fails). If this is not set, then job state files will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state directory. -x509-cert-dir PATH Set the path to the X.509 trusted certificate directory on the job execution hosts. If not present, then the trusted certificate directory used by the job manager (usually set by the Gatekeeper) will be used -seg-module MODULE Use the named module as a way to interact with the scheduler instead of polling for job status. -audit-directory DIRECTORY Store job auditing records in DIRECTORY. This directory should be sticky and group writable but not group readable. Audit records can be uploaded to a database by using the globus-gram-audit command. -globus-toolkit-version VERSION-STRING Use the string VERSION-STRING as the toolkit version in audit records. -enable-syslog Send log messages to the system log. -stdio-log LOG_DIRECTORY Obsolete way to set the directory for writing log messages. Messages will be written to LOG_DIRECTORY/gram_DATE.log. Use -log-pattern instead -log-pattern PATTERN RSL-substituted pattern for naming log files. Possible variables are HOME, LOGNAME, DATE. The -stdio-log is equivalent to -log-pattern /tmp/buildd/gram_.log -log-levels [FATAL|ERROR|WARN|DEBUG|INFO|TRACE] List of log levels to enable site-wide. These may be joined by the '|' character. Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_configuration(3)
Man Page

Featured Tech Videos