SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Could anyone tell my why my Slack system slows down after a couple hours of being online? When i say slows down I am referring to the window manager (GUI) not responding as fast as it does running as root and Mozilla slows down as well. Thanks
I'm having something similar, I left my pc on overnight last night with nothing running. when I came back to it it was running slow as a dog, it took over half an hour to compile grip!! I rebooted and everything back to normal, no idea what caused it though
i don't know if this help. but i have a very very bad machine, i mean 350 Mhz, 262 Ram, k6/amd. is an old box as you see, i install slackware 9.1 in it, and before it supposed to happen the same as all of you, after hours of running slack slow a little bit. in that time i have a web server running, and have a lot of connection request all the day and i think that all that connection to the database slow down my box cause when i delete web server it came to the fast normality that slack have, then after certain time it came back to be slow, i see was the baghira theme so i don't use baghira. the same way happens when i use superkaramba moving themes it slow down my box, so i don't use moving karamba themes. i also buy more fans to refresh more my hardware (motherboard, processor, etc) and voila slack doesn't slow down anymore. i even have put back the web server, and having a lot of connection, but whit the 3 extra fans refreshing my stuff it doesn't slow anymore.
well, take a look at /var/log/ directory, how big is it??
now take a look at /
what I'm getting at is this.......If you run a server, /var/log may be getting
a little on the heavy side.......is your /var on a seperate partition.......so as
your logs fill up they won't clog up the / partiton..........slowing down
the whole system.
yes you should check var/logs only i don't think the log will slow down your box, but it is possible that if you have a webserver running in the default /var/www/htdocs whit a lot of request and var is in the same partition than / maybe this will slow down all your system. you should check all that, what server stuff you are running if you have, check if some software is overload things like that. if you want your logs to not go very big edit /etc/logrotate
init process can be altered by editing scripts located in /etc/rc.d
After the kernel is uncompressed, when you see INIT version x.x, then init
begins by looking at /etc/inittab and then begins running scripts in /etc/rc.d
first, rc.S (which calls rc.modules) then rc.M (which calls rc.local)
Study what's happening in these scripts.
Search for recent posts on optimization