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.
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 gateway has Slackware 10.1. I found out that directory /var/spool/clientmqueue contains enormous amount of files. When I run "ls -ld /var/spool/clientmqueue", the size was about 33MB. I became worried that some coruption occured on filesystem, took out the hard drive, put it in faster machine, and ran reiserfsck (the filesystem is reiserfs). It was more than an hour ago and it is still working. I am afraid it will not finish soon, and I need internet connection.
reiserfsck is checking semantic three and outputs files from /var/spool/clientmqueue.
Do you think it is filesystem corruption, or some program is trying to send many emails, some virus or something? I don't run sendmail or other MTA.
If it is not filesystem corruption, is it safe to stop fsck? I could just delete the dir while the machine is running, I don't care how long would it take.
I don't know reiser too well to be able to advise you to stop a fsck in the middle...
When your system is up and running again, you should check if your sendmail queue runner is active - that is the process that empties the clientmqueue at regular intervals.
ps axw|grep clientmqueue
should show something like
19526 ? Ss 0:01 sendmail: Queue runner@00:25:00 for /var/spool/clientmqueue
This sendmail process is started from /etc/rc.d/rc.sendmail.
If the clientmqueue had thousands of files unfortunately it has to process each inode and that takes quite a while.
It doesn't sound like corruption though. You can look at the files - if they are mail files as they're supposed to be you should be able to just cat some examples to verify that's what they are. It should be safe to delete them but before you do you should see what the latest date is. If you're not running MTA and have thousands of files there it sounds like something is trying to send and that might mean you got hit by a spammer.