02-10-2011
Without seeing your code I can't guess why it's still open, but something must have been left open somewhere. Remember that, if it's a server socket, you've already bound it and can just accept() new connections without reopening it.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I wish to know whether a particular port is free or not in my SUN solaris SPARC machine . I wish to use that particular port for one server software.
How do I know that. (2 Replies)
Discussion started by: Hitesh Shah
2 Replies
2. Programming
how can i find whether the particular port is free among certain port numbers
like 15000 to 30000 before i connect to the server by assigning the port no for the client (0 Replies)
Discussion started by: MKSRaja
0 Replies
3. Solaris
Hi,
I have a problem one of the server file system cross the limitation
MountPoint / is 8% with 899.49MB free crossing threshold of 10% free
out put please help how to resolve this
dev/vx/dsk/bootdg/rootvol
9.8G 8.8G 956M 91% /
/devices ... (3 Replies)
Discussion started by: sriniva0
3 Replies
4. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
5. IP Networking
i want to kill a tcp connection by killing its pid
with netstat -an i got the tcp ip connection on port 5914
but when i type ps -a or ps-e there is not such process running on port 5914
is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
6. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
7. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
LISTEN(2) BSD System Calls Manual LISTEN(2)
NAME
listen -- listen for connections on a socket
SYNOPSIS
#include <sys/socket.h>
int
listen(int socket, int backlog);
DESCRIPTION
Creation of socket-based connections requires several operations. First, a socket is created with socket(2). Next, a willingness to accept
incoming connections and a queue limit for incoming connections are specified with listen(). Finally, the connections are accepted with
accept(2). The listen() call applies only to sockets of type SOCK_STREAM or SOCK_SEQPACKET.
The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full,
the client may receive an error with an indication of ECONNREFUSED. Alternatively, if the underlying protocol supports retransmission, the
request may be ignored so that retries may succeed.
RETURN VALUES
The listen() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
Listen() will fail if:
[EACCES] The current process has insufficient privileges.
[EBADF] The argument socket is not a valid file descriptor.
[EDESTADDRREQ] The socket is not bound to a local address and the protocol does not support listening on an unbound socket.
[EINVAL] socket is already connected.
[ENOTSOCK] The argument socket does not reference a socket.
[EOPNOTSUPP] The socket is not of a type that supports the operation listen().
SEE ALSO
accept(2), connect(2), socket(2)
BUGS
The backlog is currently limited (silently) to 128.
HISTORY
The listen() function call appeared in 4.2BSD.
4.2 Berkeley Distribution December 11, 1993 4.2 Berkeley Distribution