12-21-2005
Quote:
Originally Posted by zazzybob
Take a look at
this.
Cheers
ZB
I am seeing a simialar situation on many of Solaris boxes. This link rocks, but how can see the current config?
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 DEBIAN
opensearch-discover
OPENSEARCH-DISCOVER(1) User Contributed Perl Documentation OPENSEARCH-DISCOVER(1)
NAME
opensearch-discover - Find an OpenSearch link from a given URL.
SYNOPSIS
opensearch-discover [-q] [-v] [-t TITLE] [-1|-a] [-h] [URL]
DESCRIPTION
Loads the given URL, searches it for a link to an OpenSearch description URL, and prints that URL.
OPTIONS
-q, --quiet
Give no output on errors. In this case, consult the exit code to determine errors (See "DIAGNOSTICS").
-v, --verbose
Verbose: display titles with links. Combine with -a to see all available searches
-t TITLE, --title=TITLE
Only display links matching TITLE, a case-insensitive perl regular expression. For example, -t book would match Book Search, and -t
b.*k would match Book Search or Baby Springbok.
-1, --first
Only display first (matching) link. This is the default.
-a, --all
Display all (matching) links.
-h, --help
Display a short help message.
DIAGNOSTICS
On success, prints the address of the OpenSearch description file and returns 0.
If it cannot load the given URL, it returns 1.
If the given URL does not contain a link to an OpenSearch description file, it returns 2.
If required perl modules are missing, it returns 3.
DEPENDENCIES
Requires modules from libwww-perl and HTML::Parser (Debian package libhtml-parser-perl).
BUGS
None known. Please report any found to ianb@erislabs.net
SEE ALSO
opensearch(1), opensearch-genquery(1), surfraw(1), WWW::OpenSearch(3pm), <http://www.opensearch.org/>
AUTHOR
Ian Beckwith <ianb@erislabs.net>
COPYRIGHT AND LICENSE
Copyright 2006 Ian Beckwith <ianb@erislabs.net>
Licensed under the same terms as surfraw.
perl v5.12.4 2011-07-12 OPENSEARCH-DISCOVER(1)