Sponsored Content
Special Forums IP Networking Need to know reason for connections closed in netstat -p tcp Post 302899589 by vbe on Wednesday 30th of April 2014 09:00:42 AM
Old 04-30-2014
So why did it work in your first post or was it something else? In which case you to give CORRECT information and not false the the output in such way you confuse your peer and waste their time!
 

8 More Discussions You Might Find Interesting

1. SCO

tcp port always closed in inetd

sco unix 5.0.x, several weeks ago, I add a telnet-like service in inetd.conf, it runs well for 100 network terminals. But nowdays, the terminals can connect to server successfully after booting machine, but several hours later, can not connect. "netstat -p tcp -a" can NOT find the port in... (1 Reply)
Discussion started by: shark_gao
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Thread was closed without a valid reason

Dear Administrators, I think Mr. Vino is one of your Moderators here because he closes this thread: https://www.unix.com/showthread.php?p=302086230#post302086230 without a valid reason. Rule 7 states no headhunters or recruiters, but career advice is not prohibited here i think, because it... (2 Replies)
Discussion started by: patras
2 Replies

3. SCO

all tcp are CLOSED on SCO Unix on VMWARE

Hi folks, First of all, sorry about my english, isn't the best and thks for advance. Here es my problem... I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies

4. Red Hat

How to kill all active tcp connections from an IP?

How to kill all active tcp connections from an IP? I am using CentOS (3 Replies)
Discussion started by: an00p
3 Replies

5. Solaris

How to kill the TCP ESTABLISHED connection in netstat

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)
Discussion started by: GIC1986
4 Replies

6. UNIX for Dummies Questions & Answers

TCP failed connection attempts from netstat -s

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)
Discussion started by: cache51
2 Replies

7. Solaris

Connections closed for all applications

I've recently installed Solaris 10 10/9 in a new Dell Power Edge 630. Whenever I try to telnet, ssh, or FTP TO this box FROM another box on the same network segment, the following occurs: Roughly 80% of the time I get "Unable to connect to remote host: Connection refused" The remaining 20%... (0 Replies)
Discussion started by: cvaughn
0 Replies

8. IP Networking

Connections not shown in netstat output

I have a TCPIP server application (a Vendor package) which by default allows 10 connections. It provides a parameter to allow us to increase the maximum allowable connections in case it is needed. Intermittently this application is failing with maximum number of connections reached even when there... (1 Reply)
Discussion started by: AIX_user
1 Replies
RDMA_POST_RECV(3)					   Librdmacm Programmer's Manual					 RDMA_POST_RECV(3)

NAME
rdma_post_recv - post a work request to receive an incoming message. SYNOPSIS
#include <rdma/rdma_verbs.h> int rdma_post_recv (struct rdma_cm_id *id, void *context, void *addr, size_t length, struct ibv_mr *mr); ARGUMENTS
id A reference to a communication identifier where the message buffer will be posted. context User-defined context associated with the request. addr The address of the memory buffer to post. length The length of the memory buffer. mr A registered memory region associated with the posted buffer. DESCRIPTION
Posts a work request to the receive queue of the queue pair associated with the rdma_cm_id. The posted buffer will be queued to receive an incoming message sent by the remote peer. RETURN VALUE
Returns 0 on success, or -1 on error. If an error occurs, errno will be set to indicate the failure reason. NOTES
The user is responsible for ensuring that a receive buffer is posted and large enough to contain all sent data before the peer posts the corresponding send message. The message buffer must have been registered before being posted, with the mr parameter referencing the regis- tration. The buffer must remain registered until the receive completes. Messages may be posted to an rdma_cm_id only after a queue pair has been associated with it. A queue pair is bound to an rdma_cm_id after calling rdma_create_ep or rdma_create_qp, if the rdma_cm_id is allocated using rdma_create_id. The user-defined context associated with the receive request will be returned to the user through the work completion wr_id, work request identifier, field. SEE ALSO
rdma_cm(7), rdma_create_id(3), rdma_create_ep(3), rdma_create_qp(3), rdma_reg_read(3), ibv_reg_mr(3), ibv_dereg_mr(3), rdma_post_recvv(3), rdma_post_send(3) librdmacm 2010-07-19 RDMA_POST_RECV(3)
All times are GMT -4. The time now is 10:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy