Hello MGRs,
I know I know - jeesh this guy has a lot of problems. ;-) I am fairly new
to Tru64 Unix and I have to try and help support about 75 developers, so
bear with me. Thanks to Stuart Whitby for giving me a good suggestion.
I didn't receive an answer to my question here and I was wondering if:
Is it possible to minimize the time a port stays in the CLOSE_WAIT state and
if so what is the system parameter that would do so?
Cheers,
Todd M. McGuinness
Systems Engineer
____________________________
NAGRAVISION SA
Kudelski Group
____________________________
Tel. : +41 21 732 03 11
Direct: +41 21 732 0623
Fax : +41 21 732 03 00
E-mail : mcguinness_at_nagra.com
original post
>
> Hi all,
>
> I am back with a bit of a stifling problem for one of our dev groups here.
> They do an rsh 'machine' command - the command runs, and runs for about
a
> month and then for some reason the machine that was rshed into ends up
> crashing the process.
> On the 1st machine the rsh is still active and when I run a netstat -a, I
> get 2 processes in a CLOSE_WAIT state that were essentially the 2
processes
> connected to and from the 2nd machine.
>
> Anyone have any ideas how this could happen, or how to prevent the
> CLOSE_WAIT from occuring, by perhaps a system parameter?
>
> Thanks,
>
> Todd M. McGuinness
> Systems Engineer
> ____________________________
> NAGRAVISION SA
> Kudelski Group
> ____________________________
> Tel. : +41 21 732 03 11
> Direct: +41 21 732 0623
> Fax : +41 21 732 03 00
> E-mail : mcguinness_at_nagra.com
Received on Sat Mar 02 2002 - 07:37:23 NZDT