19 messages in com.perforce.perforce-userTIME_WAIT conditions
FromSent OnAttachments
PatH...@marketguide.com17 Jun 1999 14:39 
Tony...@informix.com17 Jun 1999 15:37 
Tony...@informix.com17 Jun 1999 15:37 
PatH...@marketguide.com17 Jun 1999 16:14 
PatH...@marketguide.com17 Jun 1999 16:14 
RobC...@within.com17 Jun 1999 18:36 
Jona...@floorboard.com17 Jun 1999 21:06 
PatH...@marketguide.com18 Jun 1999 07:02 
PatH...@marketguide.com18 Jun 1999 07:02 
Jaso...@tempest.com18 Jun 1999 07:28 
PatH...@marketguide.com21 Jun 1999 12:13 
PatH...@marketguide.com21 Jun 1999 12:13 
PatH...@marketguide.com21 Jun 1999 12:13 
Chri...@perforce.com21 Jun 1999 17:12 
WesP...@softweyr.com22 Jun 1999 07:56 
Neil...@c-side.com22 Jun 1999 13:23 
Neil...@c-side.com22 Jun 1999 14:01 
PatH...@marketguide.com23 Jun 1999 07:11 
WesP...@softweyr.com23 Jun 1999 19:23 
Subject:TIME_WAIT conditions
From:PatH...@marketguide.com (PatH@marketguide.com)
Date:06/17/1999 04:14:18 PM
List:com.perforce.perforce-user

Pat Hardy wrote:

I have 130 TIME_WAIT conditions on the server where Perforce is running. I see this when I do a "netstat" on the box.

Why is this?

"TCP leaves a connection in the TIME-WAIT state after successful completion of graceful shutdown." -- Comer & Stevens, 1991

They'll drain down after some interval.

This doesn't mean that I have to recompile the kernel or something to lower the interval, do I? There must be a way to lower this value.

Thanks,

Pat

----------------- Pat Hardy - Web Developer Market Guide, Inc (NASDAQ: MARG) I haven't lost my mind; Lake Success, Long Island, NY 11042-1011 it's backed up on tape http://www.marketguide.com somewhere. Telephone: 516 327 2400 x228