Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gnugk(1) [debian man page]

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

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 <> SEE ALSO
gatekeeper.ini(5) (and HTML manual) (project homepage) (manual for latest release) (commercial support) BSD
August 7, 2011 BSD

Check Out this Related Man Page

trace(1)						      General Commands Manual							  trace(1)

       trace - trace system calls of programs

       trace [options] cmd args...

       The  command  with  no flag arguments traces for the given cmd and args all system calls made and prints a time stamp, the PID, call and/or
       return values and arguments and puts its output in the file trace.dump.

       -f filename
	       Puts dump in file filename.

       -z      Echos arguments only.

       Only one of the following option arguments can be specified at one time.

       -c#     Traces given PIDs and their children.  Up to sixteen PIDs can be specified.

       -g#     Traces given groups only.  Up to sixteen Group IDs can be specified.

       -p#     Traces given PIDs only.	Up to sixteen PIDs can be specified.

       -s#     Traces given system calls only.	Up to sixteen PIDs can be specified.

       -u#     Traces given UIDs only.	Up to sixteen PIDs can be specified.

       trace -f ls.dump ls -l /dev >ls.out
       runs the cmd ls -l /dev and puts the trace in ls.dump and output in ls.out.
       trace -f csh.trace -p $$ &
       will trace your login shell in the background. To stop the trace just send it a termination signal (that is, kill -TERM trace_pid).

       Due to security, no one, not even the super-user can trace anyone else's programs. This sort of negates some of the usefulness  of  the	-g
       and -u flags.

       The program cannot be traced.

       Only 16 numbers can be given to the -c, -p, -g, -u, and -s flags.

       The kernel configuration file must contain the following:
       options	       SYS_TRACE
       pseudo-device   sys_trace

       In addition, the superuser must use the following command sequence to create the device:
       cd /dev
       MAKEDEV trace
       If both lines are not in the configuration file or if the device is not made, the message "Cannot open /dev/trace" appears.

       /dev/trace     read only character special device for reading syscall data.

       trace.dump     default file for the system call trace data.

See Also
       open(2), close(2), ioctl(2), select(2), read(2), trace(5)

Man Page

Featured Tech Videos