[Re: [lug] Memory problem]
Justin
glowecon at netscape.net
Tue Nov 28 16:20:35 MST 2000
Well, the box has no monitor so therefore no Xserver is running. I will try
the stopping and starting of the server process's rather than just a restart,
which is what I did before.
Justin
"D. Stimits" <stimits at idcomm.com> wrote:
>
> Sometimes, depending on how you are measuring the memory use, the
> meassurements can be deceptive. Released memory will sometimes not be
> simply released, but will instead end up cached. And if you are running
> an X server, your video card memory can be measured as part of the
> system ram...if it has 32 megs and the system 128, you could see up to
> 160 megs in use. One thing I'd suggest is using a tool that
> distinguishes between just ram used, and cache. Try xosview if you can.
>
> If it turns out that you do have memory being used up, it's possible
> that one of your apps has a memory leak. Sometimes a restart mechanism
> to a daemon does not actually kill the app, but simply tells it to
> re-read its init files; if this is the case, memory won't go down after
> a restart. Try a full stop and stop.
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at http://home.netscape.com/webmail
More information about the LUG
mailing list