Well the closest I have come is decreasing the time AIX takes to close sockets in the FIN_WAIT_2 state. setting tcp_keepintvl to 30 seconds with
Code:
no -o tcp_keepintvl=30
is the best I can do for now I guess. According to IBM you cannot set it lower than 30 seconds. But that may be and probably is for the best. IBM seems to know what they're doing
I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message,
Exec format error cannot bind a name to the port.
As far as I know the port is not being used by another client.
How... (1 Reply)
Hi
Is there any way to restrict the TCP-IP port usage.
I want to restrict TCP-IP port 1500/1550 to the oracle osuser.
Tanks in advance.
Remi (2 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)
I have multiple processes running the same program on my linux machine. For each process I want to be able to use a unique (available) TCP port. I have thought of using netstat to check which ports are available for use however, the time-window between checking and selecting might expose some race... (1 Reply)
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)
I am using c to send data to a socket with the following commands:
socket = socket(AF_INET, SOCK_STREAM, ptrp->p_proto);
ioctl(socket, FIONBIO, (char *)&on);
connect(socket)
send(socket,data)
shutdown(socket, SHUT_WR);
recv(socket) //ready last of data waiting on the port
//note this is... (3 Replies)
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 have an issue with port 7331 on our Unix box that is hung, It is stuck in a listen status:
ukh-o2-jcaps1:/tstjcaps6/apptest2> netstat -a|grep 7331
tcp4 1019 0 ukh-o2-jcaps1.7331 10.230.6.7.59010 CLOSE_WAIT
tcp4 1019 0 ukh-o2-jcaps1.7331 10.230.6.7.59215 ... (7 Replies)
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)
Good morning, I need your help please
After Restarting Aps or connection, these are connections
tcp 0 0 10.80.1.26.57597 10.81.248.79.53008 ESTABLISHED
tcp 0 47 10.80.1.26.57607 10.81.248.79.53008 ESTABLISHED
tcp 0 0 ... (4 Replies)
Discussion started by: alexcol
4 Replies
LEARN ABOUT REDHAT
time
TIME(2) Linux Programmer's Manual TIME(2)NAME
time - get time in seconds
SYNOPSIS
#include <time.h>
time_t time(time_t *t);
DESCRIPTION
time returns the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds.
If t is non-NULL, the return value is also stored in the memory pointed to by t.
RETURN VALUE
On success, the value of time in seconds since the Epoch is returned. On error, ((time_t)-1) is returned, and errno is set appropriately.
ERRORS
EFAULT t points outside your accessible address space.
NOTES
POSIX.1 defines seconds since the Epoch as a value to be interpreted as the number of seconds between a specified time and the Epoch,
according to a formula for conversion from UTC equivalent to conversion on the naive basis that leap seconds are ignored and all years
divisible by 4 are leap years. This value is not the same as the actual number of seconds between the time and the Epoch, because of leap
seconds and because clocks are not required to be synchronised to a standard reference. The intention is that the interpretation of sec-
onds since the Epoch values be consistent; see POSIX.1 Annex B 2.2.2 for further rationale.
CONFORMING TO
SVr4, SVID, POSIX, X/OPEN, BSD 4.3
Under BSD 4.3, this call is obsoleted by gettimeofday(2). POSIX does not specify any error conditions.
SEE ALSO ctime(3), date(1), ftime(3), gettimeofday(2)Linux 2.0.30 1997-09-09 TIME(2)
09-24-2008
