I have tried <=, does not help.
I have also tried removing TEMP_FAILURE_RETRY, nothing changes.
More strange is fact, that when I execute this first time on the client side (of course during server breakdown) it behaves like nothing happened. When I execute this second time (I have some menu which handles different operations, every operation uses communicate to exchange messages with server), I have noticed that while executing:
it kills my program! Now I am totally confused.
Hi,
We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower.
What i mean to say is since the send() function in the server program (it is... (2 Replies)
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Hi Experts,
need help about release or refresh TCP Connection:
i have the sample like below :
application log connection:
0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00
0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Hello,
I am trying to write a script in Perl which will send some data from a UNIX Box to a windows box. I am planning to create a TCP/IP communication port for the same. How do I go about this? Kindly help.
Regards,
Garric (50 Replies)
Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Hello,
Actually there are some bugs in application which does not close the TCP connection to other server though CORBA.
We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED
Is there any... (4 Replies)
Dear experts,
I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers.
How can I pin point what connection failed and what are the ports involved?
Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"?
... (2 Replies)
Why this happens?
How to solve this?
$netstat -na |grep 9325
tcp 0 0 127.0.0.1:9325 127.0.0.1:9325 ESTABLISHED
When a client socket repeatedly tries to connect to an inactive(no server socket is listening on this port) local port,connect succeeds.
... (1 Reply)
Hi,
I use solaris Unix .
I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740
root@XX # netstat -an | grep CLOSE_WAIT | wc -l
285
root@XX # netstat -an | grep CLOSE_WAIT
10.158.35.4.34805 ... (2 Replies)
I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies
LEARN ABOUT DEBIAN
tcplisten
TCPCONNECT(1) General Commands Manual TCPCONNECT(1)NAME
tcplisten - general TCP/IP server
SYNOPSIS
tcplisten [-irv] [localaddr] port
DESCRIPTION
tcplisten waits for a TCP/IP connection on port. If a localaddr parameter is given, tcplisten will bind to that IP address. Otherwise
tcplisten will accept connections to any of the local machines IP addresses. Data received from the client is printed on standard output,
and data read from standard input is sent to the client. When end-of-file is reached on both standard input and the TCP/IP connection,
tcplisten terminates.
OPTIONS -i Terminate at end-of-file on standard input; don't wait for the client to close the connection.
-r Terminate when the remote client closes the connection; don't wait for end-of-file on standard input.
-v Verbose mode. Prints a message to standard error about the origins (host and port) of the client.
SEE ALSO tcpconnect(1), telnet(1), mini-inetd(1), tcpbug(1).
BUGS
The names of the options are not yet finalized, and may change at a future release.
1997 April 13 TCPCONNECT(1)