Re: PM2e-30/ComOS-3.3.2: ... memory leak

CNSnet Tech Lib (techlib@cnsnet.net)
Mon, 23 Dec 96 11:00:28 -0000

Folks -

A few more comments since I'm in the mail mood. These relate to the
memory leak problem I commented on a few minutes back.

>From: Bruce Komito <brucek@sierra.net>
>Date: Sat, 21 Dec 1996 09:47:45 -0800 (PST)
>Subject: Re: PM2e-30/ComOS-3.3.2: telnet refused, dialup unreliable --
>memory leak?
>
>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 telnet all the time and have yet to see a problem from it. Every once
in a while I review for any "dead" telnet sessions via the "sho netconns"
command. As mentioned by others here, "res n<id>" will clean the debris
from the system with no noticable memory problems.

Still, it *would* be nice if these could idle off like other connections
to the system. User-definable, of course.

>From: Administrator <admin@emporium.on.ca>
>Date: Sat, 21 Dec 1996 15:22:51 -0500
>Subject: Re: PM2e-30/ComOS-3.3.2: telnet refused, dialup unreliable --
>memory leak?
>>
>Command> ver
>Livingston Enterprises PortMaster Version 3.3.1
>System uptime is 84 days 3 hours 26 minutes

Wow! I had mine up to about 53 days once, then upgraded from 3.3.1 to
3.3.2. Now my record is about 29 days before I took on a client who
causes me problems on a weekly basis due to his ISDN connection not
locking in (see previous note). I set up a CRON reboot job to run 3
times a week in my "offense is defense" ploy to maintain system
performance.

Any of these trophy uptimes serve ISDN? What ComOS rev? How much
memory? Tell us your secrets.

On Sat, 21 Dec 1996, Jacob Suter wrote:

> Like a fool I installed 3.3.5-B17 on my PM2-ER-10.
^^^^ ^^^

'Nuff said. OK, OK, my apologies to you, Jacob. I, for one, am thankful
that someone else has taken the point position on the bleeding edge so I
can heal my own wounds from performing that task in the past. If you
hadn't encountered the problem, we all would be after installing the
non-beta release. Thanks.

Rusty Simmons
Cimarron Network Services, Inc.
http://www.CNSnet.net/