Hi,
I need to retrieve the exit status of 4 moves running as background processes. The wait command will not work since it can only give me the exit status of the last of the background processes.
Here's a sample of what I need
!#/bin/ksh
mv /dir1/subdir1/*.Z /dir6/subdir6/ &
mv... (2 Replies)
Hi,
I have an application with a bug in it that keeps sockets in CLOSE_WAIT, which eventually freezes the server because the user account it runs under runs out of file handles. We have the bug fixed but can only release the fix with the next release.
Does anyone know how I can clear the... (3 Replies)
There is a server and a client,when client send a message to server,server can send a reply to client. The status of server and client is ESTABLISHED.Then I halt the client,I find the server status is CLOSE_WAIT and the client status is FIN_WAIT_2. Many minutes passed,I find the the server status... (1 Reply)
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Does anyone know if there is a C API call to get the status of a TCP port? As opposed to running netstat and parsing the results. At the moment I have to attempt to bind() and pick up on the address in use error which isn't very elegant
Thanks
---------- Post updated at 10:42 AM ----------... (0 Replies)
Hello Friends,
Hope you are doing well.
I just need a help in executing multiple processes.
I've written a shell script which calls another scritps. But the problem is there are too many processes to run, and each process takes about a min to finish its execution.
So, I want to just... (3 Replies)
Hi
The clients connect to my server -using port 9130. But no client could connect to my server at this time. I've checked already and this is the result
netstat -Aan|grep -v 127.0.0.1|grep 9130|pg
f10006000abcb398 tcp4 10313 0 10.0.89.81.9130 10.158.70.24.1705 CLOSE_WAIT... (8 Replies)
Discussion started by: bobochacha29
8 Replies
LEARN ABOUT DEBIAN
ibv_uc_pingpong
IBV_UC_PINGPONG(1) USER COMMANDS IBV_UC_PINGPONG(1)NAME
ibv_uc_pingpong - simple InfiniBand UC transport test
SYNOPSIS
ibv_uc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx depth] [-n iters] [-l sl] [-e] HOSTNAME
ibv_uc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx depth] [-n iters] [-l sl] [-e]
DESCRIPTION
Run a simple ping-pong test over InfiniBand via the reliable connected (RC) transport.
OPTIONS -p, --port=PORT
use TCP port PORT for initial synchronization (default 18515)
-d, --ib-dev=DEVICE
use IB device DEVICE (default first device found)
-i, --ib-port=PORT
use IB port PORT (default port 1)
-s, --size=SIZE
ping-pong messages of size SIZE (default 4096)
-r, --rx-depth=DEPTH
post DEPTH receives at a time (default 1000)
-n, --iters=ITERS
perform ITERS message exchanges (default 1000)
-l, --sl=SL
use SL as the service level value of the QP (default 0)
-e, --events
sleep while waiting for work completion events (default is to poll for completions)
SEE ALSO ibv_rc_pingpong(1), ibv_ud_pingpong(1), ibv_srq_pingpong(1)AUTHORS
Roland Dreier
<rolandd@cisco.com>
BUGS
The network synchronization between client and server instances is weak, and does not prevent incompatible options from being used on the
two instances. The method used for retrieving work completions is not strictly correct, and race conditions may cause failures on some
systems.
libibverbs August 30, 2005 IBV_UC_PINGPONG(1)