lkolchin wrote:
> Thanks for the info,
> Actually I had this problem only once and since when I run:
> */40 * * * * /bin/bash -c "(find /var/spool/amavis -type d -name 'amavis-*'
> -prune -mmin +30 -exec rm -rf {} \;)"
> As a cron job, so this won't happen again and full up my diskspace.
This just covers up the symptoms of a problem, it does not solve the
problem. On a system that works properly this type of action is
unnecessary. I would suggest running the file utility against the
files in a temporary directory containing preserved evidence as
suggested and see what happens. You hay need to disable the cron
entry shown above in order to avoid deleting preserved evidence.
Gary V
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
