ebug_client(1p) [debian man page]

EBUG_CLIENT(1p) 					User Contributed Perl Documentation					   EBUG_CLIENT(1p)

NAME

       ebug-client - Debugger client for remote debugging Perl script

SYNOPSIS

       ebug-client -key <secret> -port <port>

DESCRIPTION

       ebug-client is an debugger front end for attaching to remotely executing perl script, running on ebug-server.

       To invoke ebug-client, you must first invoke ebug-server to run debuggee and generate "key" and "port" needed for connection.  When ebug-
       server is invoked, it will show exact command-line to invoke ebug-client.

EXAMPLE

	# Attach to ebug-server running on port 4023, with key "begripra"
	$ ebug-client -key begripra -port 4023

NOTE

       Currently, you cannot "restart" debuggee. You'll need to restart one manually by re-invoking both ebug-server and ebug-client.

       Since Devel::ebug::Backend listens to "localhost" socket, you will need to relay I/O using tool like socat for true remote debugging.

       Internally, thanks for it being free software, it is almost a complete ripoff of Devel::ebug source.

SEE ALSO

       Devel::debug, ebug, ebug-server

AUTHOR

       Taisuke Yamada, <tyamadajp!list!rakugaki!org>

perl v5.14.2							    2012-03-11							   EBUG_CLIENT(1p)

IBSYSSTAT(8)							OpenIB Diagnostics						      IBSYSSTAT(8)

NAME

       ibsysstat - system status on an InfiniBand address

SYNOPSIS

       ibsysstat  [-d(ebug)]  [-e(rr_show)]  [-v(erbose)]  [-G(uid)] [-C ca_name] [-P ca_port] [-s smlid] [-t(imeout) timeout_ms] [-V(ersion)] [-o
       oui] [-S(erver)] [-h(elp)] <dest lid | guid> [<op>]

DESCRIPTION

       ibsysstat uses vendor mads to validate connectivity between IB nodes and obtain other information about the IB node. ibsysstat  is  run	as
       client/server. Default is to run as client.

OPTIONS

       Current supported operations:
	       ping - verify connectivity to server (default)
	       host - obtain host information from server
	       cpu  - obtain cpu information from server

       -o, --oui
	      use specified OUI number to multiplex vendor mads

       -S, --Server
	      start in server mode (do not return)

COMMON OPTIONS

       Most  OpenIB  diagnostics  take the following common flags. The exact list of supported flags per utility can be found in the usage message
       and can be shown using the util_name -h syntax.

       # Debugging flags

       -d      raise the IB debugging level.
	       May be used several times (-ddd or -d -d -d).

       -e      show send and receive errors (timeouts and others)

       -h      show the usage message

       -v      increase the application verbosity level.
	       May be used several times (-vv or -v -v -v)

       -V      show the version info.

       # Addressing flags

       -G      use GUID address argument. In most cases, it is the Port GUID.
	       Example:
	       "0x08f1040023"

       -s <smlid>      use 'smlid' as the target lid for SM/SA queries.

       # Other common flags:

       -C <ca_name>    use the specified ca_name.

       -P <ca_port>    use the specified ca_port.

       -t <timeout_ms> override the default timeout for the solicited mads.

       Multiple CA/Multiple Port Support

       When no IB device or port is specified, the port to use is selected by the following criteria:

       1. the first port that is ACTIVE.

       2. if not found, the first port that is UP (physical link up).

       If a port and/or CA name is specified, the user request is attempted to be fulfilled, and will fail if it is not possible.

AUTHOR

       Hal Rosenstock
	      <halr@voltaire.com>

OpenIB								  August 11, 2006						      IBSYSSTAT(8)