12-19-2005
remove CLOSE_WAIT connections
Hi folks.
I have a problem that I need to remove CLOSE_WAIT connections.
On AIX version 5.x, I can use rmsock command.
Is there a similar command on Solaris ? Is there an other solution for this situation ?
Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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)
Discussion started by: rein
3 Replies
2. UNIX for Advanced & Expert Users
Hi Guys,
Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait... (3 Replies)
Discussion started by: hariza
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (0 Replies)
Discussion started by: mgmk.84
0 Replies
4. Solaris
Hi,
Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (2 Replies)
Discussion started by: mgmk.84
2 Replies
5. Solaris
Hi,
We are using a application which uses port in CLOSE_WAIT Status.
netstat -an|grep 9191
192.168.32.11.9191 192.168.32.11.54562 49152 0 49152 0 CLOSE_WAIT
192.168.32.11.9191 192.168.32.11.54564 49152 0 49152 0 CLOSE_WAIT
192.168.32.11.9191 192.168.32.11.54568 ... (2 Replies)
Discussion started by: helplineinc
2 Replies
6. Red Hat
Hi,
I am running JBOSS 6 ona RHEL5 server put it continuously crashes due to the number of CLOSE_WAIT connections on port 8080.
How can I kill the several hundred CLOSE_WAIT connections without killing the actual live "LISTENING" connection?
R,
D. (2 Replies)
Discussion started by: Duffs22
2 Replies
7. UNIX for Advanced & Expert Users
Solaris 10 Sparc:
When you got a connection locking a tcp/port, and the status is CLOSE_WAIT (for ever :wall:), you just use the tcpdrop, to close the connection.
This is a OS bug. I wrote the bug id bellow:
BUG-ID
6468753 connections stuck in CLOSE_WAIT
The patch that's correct the bug:... (0 Replies)
Discussion started by: thiagofborn
0 Replies
8. Shell Programming and Scripting
Hello Friends,
First of all im sorry for spending extra space in DB of forum with this thread, i know there would be a solution if i kept searching,
I need to terminate the process which causes CLOSE_WAIT status of TCP connection via port 8103:
-bash-3.00$ netstat -na | grep 8103... (3 Replies)
Discussion started by: EAGL€
3 Replies
9. AIX
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
10. Solaris
Hi,
We are using a application which uses port in CLOSE_WAIT Status.
netstat -an|grep 9191
192.168.32.11.9191 192.168.32.11.54562 49152 0 49152 0 CLOSE_WAIT
192.168.32.11.9191 192.168.32.11.54564 49152 0 49152 0 CLOSE_WAIT
192.168.32.11.9191 192.168.32.11.54568 49152 0 49152 0 CLOSE_WAIT... (5 Replies)
Discussion started by: SHIV&JYOTI
5 Replies
LEARN ABOUT SUSE
unclutter
UNCLUTTER(1X) UNCLUTTER(1X)
NAME
unclutter - remove idle cursor image from screen
SYNOPSIS
unclutter [-display|-d display] [-idle seconds] [-keystroke] [-jitter pixels] [-grab] [-noevents] [-reset] [-root] [-onescreen] [-not] name
...
DESCRIPTION
unclutter removes the cursor image from the screen so that it does not obstruct the area you are looking at after it has not moved for a
given time. It does not do this if the cursor is in the root window or a button is down. It tries to ignore jitter (small movements due
to noise) if you have a mouse that twitches.
OPTIONS
-display
is followed by the display to open.
-idle is followed by the number of seconds between polls for idleness. The default is 5.
-keystroke
tells unclutter not to use a timeout to determine when to remove the cursor, but to instead wait until a key has been pressed
(released, really).
-jitter
is followed by the amount of movement of the pointer that is to be ignored and considered as random noise. The default is 0.
-grab means use the original method of grabbing the pointer in order to remove the cursor. This often doesn't interoperate too well with
some window managers.
-noevents
stops unclutter sending a pseudo EnterNotify event to the X client whose cursor has been stolen. Sending the event helps programs
like emacs think that they have not lost the pointer focus. This option is provided for backwards compatibility in case some
clients get upset.
-reset resets the timeout for idleness after the cursor is restored for some reason (such as a window being pushed or popped) even though
the x y coordinates of the cursor have not changed. Normally, the cursor would immediately be removed again.
-root means remove the cursor even if it is on the root background, where in principle it should not be obscuring anything useful.
-onescreen
restricts unclutter to the single screen specified as display, or the default screen for the display. Normally, unclutter will
unclutter all the screens on a display.
-not is followed by a list of window names where the cursor should not be removed. The first few characters of the WM_NAME property on
the window need to match one the listed names. This argument must be the last on the command line.
LIMITATIONS
The -keystroke option may not work (that is, the cursor will not disappear) with clients that request KeyRelease events. Games and Xt
applications using KeyUp in their translation tables are most likely to suffer from this problem. The most feasible solution is to extend
unclutter to use the XTest extension to get all keyboard and mouse events, though this of course requires XTest to be in the server too.
The -keystroke option does not distinguish modifier keys from keys which actually generate characters. If desired this could be imple-
mented in a simple way by using XLookupString to see if any characters are returned.
DIAGNOSTICS
The message
someone created a sub-window to my sub-window!
means that unclutter thinks a second unclutter is running, and tried to steal the cursor by creating a sub-window to the sub-window already
used to steal the cursor. This situation quickly deteriorates into a fight no one can win, so it is detected when possible and the program
gives up.
AUTHOR
Mark M Martin. cetia 7feb1994. mmm@cetia.fr
UNCLUTTER(1X)