try setting tcp_time_wait_interval to the value of 1000 (1 second)

/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 1000

David

-----Mensagem original-----
De: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]Em nome de Darren Dunham
Enviada em: terca-feira, 23 de novembro de 2004 15:44
Para: Veritas-bu AT mailman.eng.auburn DOT edu
Assunto: Re: [Veritas-bu] 'hanging' bprd - ports in CLOSE_WAIT state


> Thanks to all who responded - I double-checked my startup script: I am
using tcp_time_wait_interval (not close_wait).
>
> The customer is still battling with the same problem :
>
> bprd hangs - ports remain in CLOSE_WAIT state for hours (see details
below).

CLOSE_WAIT state I generally associate with a bug in the application or
the TCP stack of the host.  It means the network connection has been
torn down, but the local process needs to acknowledge that and clean
up.

tcp_time_wait_interval will have no effect on this.

Do you have all relevant NBU and OS patches applied?

--
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu