Re: Telnet connections - the connection drops, the process doesn't die!
- From: Jim <mckinneyj@xxxxxxxx>
- Date: Thu, 10 Apr 2008 10:59:49 -0700 (PDT)
On Apr 10, 11:29 am, etmsr...@xxxxxxxxxxx wrote:
Hiya,
We have a client using OpenVMS v8.3 on Integrity running TCP/IP
Services v5.6 ECO2. Our connection goes over a line that disconnects
idle sessions after 30 minutes. this part works well, but it seems
that VMS doesn't terminate the process in the case of a telnet session
that gets disconnected. Over time, there are dozens of processes left
lying around with no terminal attached to them.
Similarly, we have a client with OpenVMS v7.3-1 on Alpha with V5.3 Eco
4 which has users on the local LAN which get left with "ghost"
sessions - the process is still there on the Alpha but the terminal
device has gone away.
Anyone got any ideas how this can be resolved? I've tried setting the
socket options to nokeepalive but this doesn't appear to do the trick.
Thanks in advance
Steve
I don't have your cure, but, you state that you disabled keepalives -
to catch broken connections you actually want to enable them in order
so that your system will send out keepalive probes. When these
keepalive probes repeatedly go unanswered the connection should be
disconnect (if the stack behaves correctly). Typically the default
behavior of keepalives is that after 2 hours of inactivity probes are
sent out on a 75 second interval - and if 10 consecutive probes are
unanswered the connection is declared dead and terminated. If any
probe is answered then the 2 hour idle timer begins again.
.
- References:
- Prev by Date: Re: Orange Light on SCSI drive
- Next by Date: Re: Orange Light on SCSI drive
- Previous by thread: Re: Telnet connections - the connection drops, the process doesn't die!
- Next by thread: Re: Telnet connections - the connection drops, the process doesn't die!
- Index(es):
Relevant Pages
|
Loading
