Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian 6 (Squeeze), changed from Fedora 14 after they went to 15
Posts: 4
Rep:
Memory
Problem; each time I open a program then close the program it is remaining in memory. (using the system monitor) I am being forced to reboot about every 45 minutes as the cache continues to build up.
In windows I used a program called "CustomizerXP" which allowed me to right click an icon and free-up memory by dumping the cache.
Is there a similar program for Fedora 10 or how do I dump cache without rebooting so often?
I am being forced to reboot about every 45 minutes as the cache continues to build up.
Why ? Do you have a real problem, or just an imagined problem ?.
This comes up continually from (ex-)Windoze users that don't understand Linux memory management. Read this - ignore the bit on swappiness for now.
Distribution: Debian 6 (Squeeze), changed from Fedora 14 after they went to 15
Posts: 4
Original Poster
Rep:
memory
Well Mr. syg00,
the reason for having to reboot is because my computer locks up. It's not that I can quit and restart. I have to power off manually. This is a laptop but should be quite capable of running f10. 1.8 GHz CPU, 1Gb memory, 80Gb HDD. just the basics but should tell you enough to help me figure out why I lock up about every 45 minutes or so while I am not doing any hard-core graphics or cad renderings. I am just surfing the web and usually have anywhere from 6-15 tabs open at one time plus pidgin running and chatting with anywhere from 1-4 people at once. Why is this happening?
Distribution: Slackware (mainly) and then a lot of others...
Posts: 855
Rep:
hi rongaines,
I do not know if this is the answer but you can kill a process that is running on your pc. Yoy can use kill when using 'top' or 'htop' and that should kill the process. Read the man page of kill to see how yoyu can kill with a SIGTERM.
What I really dont understand is why is the process alive and running when you have obviously killed it.
It's not that I can quit and restart. I have to power off manually. This is a laptop but should be quite capable of running f10. 1.8 GHz CPU, 1Gb memory, 80Gb HDD.
Well, that certainly sounds like a real problem. Doesn't make a lot of sense though - as you said, that should run Fedora 10 easily.
Quote:
just the basics but should tell you enough to help me figure out why I lock up about every 45 minutes or so while I am not doing any hard-core graphics or cad renderings.
Nope - we need some hard evidence; error messages or somesuch. What makes you think cache is the problem ?
Closing the programs should remove them from the monitor - at least it does on this F10 system. Does killing them fix it ???.
Next time you have to reboot, run this and post the output hopefully it'll have something useful
This sounds like a flaky memory stick to me. I would try running memtest86 on it overnight. An iffy memory stick can cause all kinds of issues, trouble burning DVDS, random screw ups, etc. Besides it is an easy and cheap thing to check.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.