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.
Using Mandrake 9.0 I noticed something diffrent from 8.2:
My /var/log/syslog and /var/ log/kernel/info get longer than 4 Gig each. A few days ago I cleared them, and today they are more then 2.5 Gig again !
My / partition is 20G but it fills up quickly as both those files grow over 8G !
Anyone an idea ?
( the /var/log/messages has a fixed length, as lines are added, the disapear at the top )
Hmm. You better find out what's filling your logs.
For instance if your entry looks like this:
kern.=debug;kern.=info;kern.=notice /var/log/kernel/info
it means everything from the informational level (6) and up will be logged:
Code:
# loglevel defined in <linux/kernel.h>:
# KERN_EMERG "<0>" /* system is unusable */
# KERN_ALERT "<1>" /* action must be taken immediately */
# KERN_CRIT "<2>" /* critical conditions */
# KERN_ERR "<3>" /* error conditions */
# KERN_WARNING "<4>" /* warning conditions */
# KERN_NOTICE "<5>" /* normal but significant condition */
# KERN_INFO "<6>" /* informational */
# KERN_DEBUG "<7>" /* debug-level messages */
To quickly see what DOSses your logs you could add this entry (check your tab usage) and restart syslogd (kill -HUP syslog):
kern.info /dev/tty12
This will log all messages with the kern facility from info level up into your log (as the first rule shows) but also to tty12 (switch to it with ALT+CTRL+F12). Watch the output for over and over repeating lines.
(same goes for the /var/log/syslog , all kind of ppp messages)
I've got that damn Speedtouch USB modem, I think that's filling my logs !
I have found a solution myself: rm /var/log/kernel/info and rm /var/log/syslog once a day with kcron. It builts a new log automaticly.
Thanks unSpawn, looks like a good tip.
my /etc/ppp/peers/adsl says: kdebug 1 I'll change that to 0
I recieved another interesting tip at Mandreke-Club forum:
Anacron !
As my computer is not on 24 hrs a day, cron-jobs like logrotate are forgotten because they run at 4 o'clock in the morning. Anacron detects forgotten cron-jobs and executes them shortly after boot. ( updatedb is another forgotten job )
It looks there are quiet some other jobs that have to run at night, once a week or once a month, if anyone has an idea what those jobs might be, let me know, I got curious now !
Anacron was installed by default in MDK 8.1 and 8.2 but not in MDK 9.0
For those of you who's computer is not up 24/7 :
urpmi anacron (CD 3)
makewhatis - create a whatis database
postfix - check for problems
slocate - the aplication that updatedb points
tmpwatch - cleans the old/unused files in tmp
and anacron itself
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.