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-GATEKEEPER(8)						  Globus Toolkit					      GLOBUS-GATEKEEPER(8)

NAME
globus-gatekeeper - Authorize and execute a grid service on behalf of a user SYNOPSIS
globus-gatekeeper [-help] [-conf PARAMETER_FILE] [-test] [-d | -debug] {-inetd | -f} [-p PORT | -port PORT] [-home PATH] [-l LOGFILE | -logfile LOGFILE] [-lf LOG_FACILITY] [-acctfile ACCTFILE] [-e LIBEXECDIR] [-launch_method {fork_and_exit | fork_and_wait | dont_fork}] [-grid_services SERVICEDIR] [-globusid GLOBUSID] [-gridmap GRIDMAP] [-x509_cert_dir TRUSTED_CERT_DIR] [-x509_cert_file TRUSTED_CERT_FILE] [-x509_user_cert CERT_PATH] [-x509_user_key KEY_PATH] [-x509_user_proxy PROXY_PATH] [-k] [-globuskmap KMAP] [-pidfile PIDFILE] DESCRIPTION
The globus-gatekeeper program is a meta-server similar to inetd or xinetd that starts other services after authenticating a TCP connection using GSSAPI and mapping the client's credential to a local account. The most common use for the globus-gatekeeper program is to start instances of the globus-job-manager(8) service. A single globus-gatekeeper deployment can handle multiple different service configurations by having entries in the /etc/grid-services directory. Typically, users interact with the globus-gatekeeper program via client applications such as globusrun(1), globus-job-submit, or tools such as CoG jglobus or Condor-G. The full set of command-line options to globus-gatekeeper consists of: -help Display a help message to standard error and exit -conf PARAMETER_FILE Load configuration parameters from PARAMETER_FILE. The parameters in that file are treated as additional command-line options. -test Parse the configuration file and print out the POSIX user id of the globus-gatekeeper process, service home directory, service execution directory, and X.509 subject name and then exits. -d, -debug Run the globus-gatekeeper process in the foreground. -inetd Flag to indicate that the globus-gatekeeper process was started via inetd or a similar super-server. If this flag is set and the globus-gatekeeper was not started via inetd, a warning will be printed in the gatekeeper log. -f Flag to indicate that the globus-gatekeeper process should run in the foreground. This flag has no effect when the globus-gatekeeper is started via inetd. -p PORT, -port PORT Listen for connections on the TCP/IP port PORT. This option has no effect if the globus-gatekeeper is started via inetd or a similar service. If not specified and the gatekeeper is running as root, the default of 2119 is used. Otherwise, the gatekeeper defaults to an ephemeral port. -home PATH Sets the gatekeeper deployment directory to PATH. This is used to interpret relative paths for accounting files, libexecdir, certificate paths, and also to set the GLOBUS_LOCATION environment variable in the service environment. If not specified, the gatekeeper looks for service executables in /usr/sbin, configuration in /etc, and writes logs and accounting files to /var/log. -l LOGFILE, -logfile LOGFILE Write log entries to LOGFILE. If LOGFILE is equal to logoff or LOGOFF, then logging will be disabled, both to file and to syslog. -lf LOG_FACILITY Open syslog using the LOG_FACILITY. If not specified, LOG_DAEMON will be used as the default when using syslog. -acctfile ACCTFILE Set the path to write accounting records to ACCTFILE. If not set, records will be written to the log file. -e LIBEXECDIR Look for service executables in LIBEXECDIR. If not specified, the sbin subdirectory of the parameter to -home is used, or /usr/sbin if that is not set. -launch_method fork_and_exit|fork_and_wait|dont_fork Determine how to launch services. The method may be either fork_and_exit (the service runs completely independently of the gatekeeper, which exits after creating the new service process), fork_and_wait (the service is run in a separate process from the gatekeeper but the gatekeeper does not exit until the service terminates), or dont_fork, where the gatekeeper process becomes the service process via the exec() system call. -grid_services SERVICEDIR Look for service descriptions in SERVICEDIR. -globusid GLOBUSID Sets the GLOBUSID environment variable to GLOBUSID. This variable is used to construct the gatekeeper contact string if it can not be parsed from the service credential. -gridmap GRIDMAP Use the file at GRIDMAP to map GSSAPI names to POSIX user names. -x509_cert_dir TRUSTED_CERT_DIR Use the directory TRUSTED_CERT_DIR to locate trusted CA X.509 certificates. The gatekeeper sets the environment variable X509_CERT_DIR to this value. -x509_user_cert CERT_PATH Read the service X.509 certificate from CERT_PATH. The gatekeeper sets the X509_USER_CERT environment variable to this value. -x509_user_key KEY_PATH Read the private key for the service from KEY_PATH. The gatekeeper sets the X509_USER_KEY environment variable to this value. -x509_user_proxy PROXY_PATH Read the X.509 proxy certificate from PROXY_PATH. The gatekeeper sets the X509_USER_PROXY environment variable to this value. -k Use the globus-k5 command to acquire Kerberos 5 credentials before starting the service. -globuskmap KMAP Use KMAP as the path to the Grid credential to kerberos initialization mapping file. -pidfile PIDFILE Write the process id of the globus-gatekeeper to the file named by PIDFILE. ENVIRONMENT
If the following variables affect the execution of globus-gatekeeper: X509_CERT_DIR Directory containing X.509 trust anchors and signing policy files. X509_USER_PROXY Path to file containing an X.509 proxy. X509_USER_CERT Path to file containing an X.509 user certificate. X509_USER_KEY Path to file containing an X.509 user key. GLOBUS_LOCATION Default path to gatekeeper service files. FILES
/etc/grid-services/SERVICENAME Service configuration for SERVICENAME. /etc/grid-security/grid-mapfile Default file mapping Grid identities to POSIX identities. /etc/globuskmap Default file mapping Grid identities to Kerberos 5 principals. /etc/globus-nologin File to disable the globus-gatekeeper program. /var/log/globus-gatekeeper.log Default gatekeeper log. SEE ALSO
globus-k5(8), globusrun(1), globus-job-manager(8) University of Chicago 01/06/2012 GLOBUS-GATEKEEPER(8)
Man Page