Today Nagios Alarm, a server disk full, use DU-SH * or du-sh/* To view the size of the directory, looking for a large space-occupying directory/var/spool/clientmqueue ....
Then just want to/var/spool/clientmqueue this directory why use, tangled up for a while, Google, the original/var/spool/clientmqueue is if the system has users open cron, and Cron executes the program has output content, The output is sent to the cron user in the form of a message, and SendMail does not start, resulting in these files.
The server does have cron timed to execute dozens of scripts, and none of the output orientations are set, and the accumulated files are saved in the/var/spool/clientmqueue directory under le = =.
Workaround: Add >/dev/null after cron automatically executes the statement 2>&1
Cases:
4 3 * * */usr/bin/w >/dev/null 2>&1
This will be OK to pull, will not write to that directory ....
Say here a little,/var/spool/clientmqueue directory file too many, RM-RF * time will prompt:
"-bash:/bin/rm:argument list too long".
It means that the parameters are too long for RM to dry.
You can use ls | xargs rm-f This command to delete all files in the/var/spool/clientmqueue directory.
Ok. Clean up.
Linux/var/spool/clientmqueue catalogue "Turn"