Thanks,
steve
sar -r
See 'man sar' for more details. If you've not previously enabled sar,
you'll have to execute "/usr/lib/sa/sar_enable -y" to start logging.
bkx
Or if you want to know how much is being used "right now":
echo o -d freemem|crash
Subtract the number this gives you from the amount of physical memory on the
system.
Also see: ftp://ftp.armory.com/pub/admin/memuse
John
--
John DuBois spc...@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/
Steve
"John DuBois" <spc...@deeptht.armory.com> wrote in message
news:3dd450fc$0$22477$8ee...@newsreader.tycho.net...
Right. I should have mentioned that freemem gives available real memory in 4K
pages, so the first output you got indicates 16920*4 = 67680KB available.
Is this also in 4K pages. The user associated with this process is a
windows XP machine.
Thank you,
steve
"John DuBois" <spc...@deeptht.armory.com> wrote in message
news:3dd5afa9$0$79559$8ee...@newsreader.tycho.net...
No, it's in units of 1 KB. So, this process all by itself is using several
times the amount of real memory you have available, and is presumably making
the system swap madly.
> The server went crazy again late friday so I ran ps -elf with the following
> result:
> vfsd --profile /usr/vision/vfsprofile and the SZ = 313032.
>
> Is this also in 4K pages. The user associated with this process is a
> windows XP machine.
`ps -l` size output is in 1K units. So that process was taking over
300MB, and was probably still growing as fast as possible (or dumping
core due to having grown too large).
Make sure you have the newest version of VisionFS, and if it's still
flaking out, talk to Tarantella about it.
>Bela<