From owner-freebsd-isp Thu Mar 14 09:22:14 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA19778 for isp-outgoing; Thu, 14 Mar 1996 09:22:14 -0800 (PST) Received: from databus.databus.com (root@databus.databus.com [198.186.154.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA19773 for ; Thu, 14 Mar 1996 09:22:12 -0800 (PST) Message-ID: <9603141222.AA23891@databus.databus.com> Date: Thu, 14 Mar 96 12:21 EST From: Barney Wolff To: Bruce Bauman , freebsd-isp@freebsd.org Subject: Re: csh hanging around after disconnect Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The terminal server is acting as a router. What is it supposed to send and to whom, when the user disconnects without closing all TCP (and other connection-oriented) sessions? The only answer to this, and not a very swift one, is to run TCP keep-alives on all telnet and poppassd sessions on your host, and that will eventually detect that the user's gone away. Barney Wolff >From: Bruce Bauman >Date: Wed, 13 Mar 1996 16:26:55 -0500 (EST) > >Hi. We're an ISP using Livingston portmasters and running 2.1-stable. Our portmasters >are set with an idle timeout of 30 minutes. I have noticed that when users get booted >off by the timeout, their csh process hangs around. Is this a bug? Or am I doing >something wrong on my end. We don't reboot our server very often, so this ends up >being a problem for us. > >Also, we run the poppassd daemon so that users can change their passwords via >Eudora. We have the same problem - if a user disconnects in the middle of >changing their password, the process hangs around forever and ties up a pty. >Does anyone have a fix for this?