clear CLOSE_WAIT status Post: 302091398

10 More Discussions You Might Find Interesting

1. Solaris

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.

2. UNIX for Advanced & Expert Users

close_wait connections causing a server to hung

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. Solaris

CLOSE_WAIT problem in solaris server

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...

4. Solaris

How to remove CLOSE_WAIT in 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 ...

5. Red Hat

Too many CLOSE_WAIT connections

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.

6. UNIX for Advanced & Expert Users

stuck in CLOSE_WAIT Solaris 10 - Patch and workaround

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:...

7. Shell Programming and Scripting

Terminate processes for CLOSE_WAIT status of TCP

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...

8. AIX

How to repair a TCP/IP socket in state: CLOSE_WAIT?

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...

9. Shell Programming and Scripting

Clear contents of specified directories, then return exit status

Hello, this is my first post here. I'm attempting to write a bash shell script to rm the contents of a directory without deleting the directory, specifically in OS X 10.10 . Here's what I have: function clear() { USER="$USER" DIR=$1 rm -rfv /Users/"$USER"/library/$DIR/* } clear...

10. Solaris

How to remove CLOSE_WAIT in Solaris 5.10?

LEARN ABOUT REDHAT

octave-bug

octave-bug(1)						      General Commands Manual						     octave-bug(1)

NAME

       octave-bug - report a bug in GNU Octave

SYNOPSIS

       octave-bug [-s subject]

DESCRIPTION

       octave-bug is a shell script to help the user compose and mail bug reports concerning Octave in a standard format.  octave-bug is typically
       invoked by the Octave command bug_report which is intended to be called interactively from within Octave. This provides	the  best  way	to
       submit  a  bug  report for Octave. It creates a template bug report file and starts an editor on that file.  The bug report will be sent to
       the bug-octave mailing list once the editing has been completed (this assumes of course that your system can use email). However, the  user
       could also call octave-bug outside of Octave.

       Please  read  the `Bugs' chapter in the Octave manual to find out how to submit a bug report that will enable the Octave maintainers to fix
       the  problem.   If  you	are  unable  to  use  the  bug_report  command,  send  your  message  to  the  bug-octave   mailing   list,   bug-
       octave@bevo.che.wisc.edu.

OPTIONS

       -s subject
	      Specify a subject line for the bug report.  Spaces in the subject must be quoted.

ENVIRONMENT VARIABLES

       octave-bug uses the environment variables USER, EDITOR, and PAGER which can be used for customization.

VERSION

       This document was last revised for Octave version 2.0.16.

SEE ALSO

       octave(1), bashbug(1)

AUTHOR

       John W. Eaton
       Department of Chemical Engineering
       University of Wisconsin-Madison
       Madison, WI 53706
       USA
       <jwe@bevo.che.wisc.edu>

GNU
								   6 March 2000 						     octave-bug(1)

10 More Discussions You Might Find Interesting

1. Solaris

remove CLOSE_WAIT connections

Discussion started by: Livio

2. UNIX for Advanced & Expert Users

close_wait connections causing a server to hung

Discussion started by: hariza

3. Solaris

CLOSE_WAIT problem in solaris server

Discussion started by: mgmk.84

4. Solaris

How to remove CLOSE_WAIT in Solaris

Discussion started by: helplineinc