From owner-freebsd-isp Sat Mar 16 07:07:44 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA06996 for isp-outgoing; Sat, 16 Mar 1996 07:07:44 -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 HAA06989 for ; Sat, 16 Mar 1996 07:07:40 -0800 (PST) Message-ID: <9603161007.AA03474@databus.databus.com> Date: Sat, 16 Mar 96 10:07 EST From: Barney Wolff To: "Miguel A.L. Paraz" Cc: 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 >From: "Miguel A.L. Paraz" >Date: Sat, 16 Mar 1996 13:49:24 +0800 (GMT+0800) > >> 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. > >How is this done? Is this a separate daemon, or an option to compile >in these daemons? See the SO_KEEPALIVE option in set/getsockopt(3N). That turns keepalives on or off, and probably needs to be in inetd, or perhaps telnetd. The interval between keepalives is a kernel parameter, and I don't know if it's tunable or you need to delve into the source. It may be on already - the default interval for keepalives is 2 hours. In the dialup IP scenario, 5 minutes is probably more useful. Barney Wolff