Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My /var partition is full its usage capacity is 100% maybe thats
why when I'm trying to run squid it was failed...
Can anybody help me how to solve it or gave me an idea on what part
should I delete so that the usage capacity will reduce something to 95% or much better
lower than that...
You should first determine what is filling up /var. If yum is doing it, check the link I gave in post #5. If 'standard' logging is filling up /var, focus on that.
The next part could be useful if standard logging is filling up /var:
You shouldn't just remove all the files in /var/log.
If logrotate is running (I believe CentOS has it running), you can change the amount of files that are kept for safe keeping. Take a look here for some more info on logrotate: Rotating Linux Log Files
And this is logrotate's manpage
The attribute that is of interest is rotate X, this tells logrotate how long (in weeks) old logfiles should be kept before removing them. If you aren't sure what to change, post your /etc/logrotate.conf file so we can have a look.
Yes, that would tell us what part of /var fills. Every case is different.. You may have a deffective program that logs a lot of garbage in /var/log.
If the previous cmd shows that /var/log is the fatty one, then get some info from /var/log: