>isdn2> sho mem
>System memory 1048576 bytes - 895172 used, 153404 available
>144:1 96:0 128:0 80:5 272:2 16:9 32:5 48:1
>System nbufs 1400 - 84 used, 1316 available
>
>...however, after a few short hours, I get to this:
>
>isdn2> sho mem
>System memory 1048576 bytes - 1048440 used, 136 available
>2048:4 160:6 1152:0 640:0 176:0 144:5 96:3 128:4 80:620 272:4 16:57 32:0 48:6
>System nbufs 1400 - 83 used, 1317 available
>Is this a known problem? Has anyone experienced anything like this? I
have physically REPLACED the PM2i and the problem persists, making me
believe this has to be some kind of a memory leak in ComOS...?
I have to chime in and say I have the exact same problem. The "leak" here
seems to be much slower.
Command> sh mem
System memory 1048576 bytes - 1029596 used, 18980 available
1152:0 640:0 4240:3 96:0 144:0 2048:0 64:0 112:1 176:1 80:3 128:1 272:5
16:101 32:2287 160:1 48:1
System nbufs 1400 - 51 used, 1349 available
Command> ver
Livingston PortMaster PM-2e ComOS 3.7.2
System uptime is 5 days 17 hours 0 minutes
All ISDN connections on this box go to a PM3. Interestingly enough, the
problem was MUCH worse with pre-3.8 software on the PM3. After a fresh
boot, the box has over 100K of available memory.
Scott
-----------------------------------------------------------
"We demand rigidly defined areas of doubt and uncertainty."
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>