Mark,
>>> Grep the log for '08540-17' and see what went wrong, i.e. what caused
>>> the later preserving of evidence. The cause should be fixed.
>>
>> I followed up on that error and I forgot to make a particular directory
>> that amavis was trying to use. Thank you for helping me to find that. I
>> still am accumulating directories in the /var/amavis/tmp directory
>> though. I am 8,000 now. I no longer have the "PRESERVING EVIDENCE" error
>> in my logs though. I have this in my amavis.conf:
>>
>> $max_servers = 5; # number of pre-forked children
>> $max_requests = 20; # retire a child after that many accepts
>>
>> I realize that while it is working on something you will see
>> directories. With 5 max servers how many directories can/will amavis
>> create simultaneously?
>
> 5 directories.
>
> Any leftovers from past failures should be removed manually,
> there is no automatism to purge them.
>
> One way to purge is:
> stop amavisd, delete all temp directories, restart amavisd
>
I followed this and now I only see 5 total directories at any one time.
Once I got the one line in my amavisd.conf fixed it has been working
like a charm.
>> Should the 8,000 directories be a concern?
>
> It's not too bad by itself. But eventually this should be
> cleaned. If new directories are accumulating, the cause should
> be examined. It should stand out in the logs.
>
>> What other reasons are there for these directories being abandoned?
>
> Crashing processes? These disappear without a trace in the log.
> Running amavisd-nanny manually every once in a while (or SNMP monitoring)
> should be able to detect and report if there were any crashes since
> the previous invocation of amavisd-nanny.
>
>> From what I could find it seems like they should be being removed/pruned
>> automatically.
>
> Yes, but only the ones still under control of sane amavisd processes.
> Any uncontrolled leftovers are abandoned by amavisd.
>
>> I have now sub categorized /var/virusmails/ the with your
>> sql_partition_tag. That is really handy. Thank you. I take it from your
>> response that the real problem ("too many" files) comes in with regards
>> to the maximum possible files in a directory for a file system and not
>> something in amavisd having some practical limit for processing speed?
>> Or am I understanding that incorrectly?
>
> Correct. As long as creating a file in such directory does not take
> excessively long time, amavisd does not care how many files there are
> in a quarantine directory.
>
> Mark
>
Seeing as it is a quarantine, other than having historical value (going
back and catching a piece of ham) is does it behoove me to keep these
files longer than X amount of time (lets just arbitrarily say a month)?
Or maybe better put: Why would I want to keep these files around for an
extended amount of time?
Also, thank you very much for your time, patience and guidance.
Peter
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
