Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tping(1) [linux man page]

TPING(1)                                                           LAM COMMANDS                                                           TPING(1)

NAME
tping - Send echo messages to LAM nodes. SYNOPSIS
tping [-hv] [-c count] [-d delay] [-l length] nodes OPTIONS
-h Print the command help menu. -v Turn OFF verbose mode. -c count Send count messages. -d delay Delay delay seconds between each message. -l length Each message is length bytes long. DESCRIPTION
The tping command sends messages to, and collects replies from, a list of nodes, via the LAM echo server. It is similar to the UNIX ping(8) command, and is used as a quick diagnosis of the LAM network. Unless options are specified, tping sends a 1 byte message an infinite number of times, displaying the roundtrip time of each message as it completes, with a delay of 1 second between roundtrips. After the loop is broken (with keyboard interrupt, eg: ^C), tping prints statis- tics about all roundtrip messages. EXAMPLES
tping h Echo messages to the local node. tping -v n7 -l 1000 -c 10 Echo 1000 byte messages to node 7. Stay silent while working. Stop after 10 roundtrips and report statistics. BUGS
There is no built-in timeout and tping will wait forever to receive an echo. If no echo is received, due to a dead link or node, tping hangs. Stop the process with a keyboard suspend signal (eg: ^Z) and terminate LAM with lamhalt(1) or lamwipe(1) (although the use of lamwipe(1) is deprecated). SEE ALSO
lamhalt(1), lamwipe(1) LAM 7.1.4 July, 2007 TPING(1)

Check Out this Related Man Page

INTROU(1)							   LAM COMMANDS 							 INTROU(1)

NAME
introu - introduction to LAM user interface commands LIST OF COMMANDS
Name Appears Description on Page bfctl bfctl.1 Control message buffers (optional). bfstate bfstate.1 Get message buffer status (optional). doom doom.1 Deliver a signal (optional). fctl fctl.1 Control remote file access (optional). fstate fstate.1 Get remote file status (optional). hboot hboot.1 Start LAM on a local node. mpicc mpicc.1 Compile LAM C programs. mpiCC mpicc.1 Compile LAM C++ programs. mpif77 mpif77.1 Compile LAM F77 programs. lamboot lamboot.1 Start LAM. lamclean lamclean.1 Clean all nodes. lamexec lamexec.1 Run non-MPI programs. lamgrow lamgrow.1 Add a node. lamhalt lamhalt.1 Terminate LAM. lamshrink lamshrink.1 Remove a node. lamtrace lamtrace.1 Unload trace data. loadgo loadgo.1 Execute program (optional). mpimsg mpimsg.1 Display MPI buffered messages. mpirun mpirun.1 Run an MPI application. mpitask mpitask.1 Display MPI processes. recon recon.1 Verify LAM setup. state state.1 Get process status (optional). sweep bfctl.1 Clean out message buffers (optional). tkill tkill.1 Terminate local node LAM session. tping tping.1 Echo messages to a node. lamwipe lamwipe.1 Terminate LAM (deprecated; use lamhalt). Node Specification Target nodes are given on the command line. Nodes are generically identified as nlist, where list can be a single node identifier or a list of node identifiers. For example: n1 n1,3,5-10 Additionally, clist can be used to list specific CPUs on a given machine (lamboot(1) is used to specify how many CPUs LAM may use on each node). Node/CPU identifiers are established in the boot schema (see bhost(5)), and can be written in decimal or hexadecimal notation. In addition to explicit node identification, LAM has special mnemonics that refer to special nodes or a group of nodes. h the local node where the command is typed (as in "here") o the origin node where LAM was started with lamboot(1) N all nodes C all CPUs Process Specification LAM processes can be specified in two ways: by process identifier from the underlying operating system or by LAM process index. PIDs are written as plist, where list can be a single PID or a list of PIDs. Process indices are written as ilist, where list can be a single index or a list of indices. LAM 7.1.4 July, 2007 INTROU(1)
Man Page