Re: PM2e-30/ComOS-3.3.2: telnet refused, dialup unreliable -- memory leak?

Bruce Komito (brucek@sierra.net)
Sat, 21 Dec 1996 14:14:37 -0800 (PST)

The problem could very well have something to do with the client or how a
session is terminated. Nevertheless, we use the same clients with our
Portmasters as we do with our Sun and BSDi systems, and our Ciscos and our
Maxs and we don't have to reboot them, so I can only conclude that it's a
vulnerability of the PM.

On Sat, 21 Dec 1996, Doug Ingraham wrote:

> On Sat, 21 Dec 1996, Bruce Komito wrote:
>
> > We've had this problem for two years and continue to have it. If you
> > routinely telnet into your PM, plan on rebooting it every 3-4 weeks as a
> > precaution. On the other hand, if you leave it alone, it will run for
> > months.
>
> I don't get it. I have never had this problem and I always telnet in.
> Several times a day per unit. I had a unit up 140 days with never a
> problem. I know what to do if it ever happens so I am not worried but
> what are you doing that causes it. I always type exit to close the
> connection at the pm prompt. The telnets are always from BSDI 2.1 or
> FreeBSD 2.1.5 or from another PM. Are you using some other telnet agent
> and just dropping the connection which causes it to hang?
>
> Doug Ingraham A Puritan is someone who absolutely cannot stand the
> Rapid City, SD idea that someone somewhere is having a good time. :-)
> USA
>