From owner-freebsd-isp Sun Feb 9 16:11:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA20759 for isp-outgoing; Sun, 9 Feb 1997 16:11:57 -0800 (PST) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20743 for ; Sun, 9 Feb 1997 16:11:43 -0800 (PST) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.4) with SMTP id TAA24961; Sun, 9 Feb 1997 19:11:36 -0500 (EST) Date: Sun, 9 Feb 1997 19:11:35 -0500 (EST) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: Peter Carah cc: isp@freebsd.org Subject: Re: Terminal Servers? (which one) In-Reply-To: <199702091839.KAA03154@news.interworld.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 9 Feb 1997, Peter Carah wrote: > 3.3.2 would reboot immediately if anyone attempted a PAP login on it. > They fixed it very quickly as 3.3.2c1 but THAT leaked memory like a sieve. > 3.3.3 is fairly stable but still leaks memory some. I haven't tried later > than that. Note that several months production got shipped with 3.3.2 in > it; you had to upgrade immediately... 3.5 fixes the memory leaks and has a usable IGP to boot. > Ours aren't quite that good. The primary cause of our reboots is the console > (pm_open or pm_term) application gets wedged and cancelled at the unix > (or windoze) end, and you cant start another till the box gets rebooted. > It would be nice to be able to kill the connection at the pm2 end without > a reboot. You can up the number of PMCrashsole connections allowed with: set maximum pmconsole where is the max concurrent sessions to allow (up to 10). You can also reset connections by telneting to the PM, doing a 'show netconns', finding the crashed connection, and resetting it with 'reset nXXX', where XXX is the number from the leftmost column of the 'show netconns'. pbd