First yes your right, i did not notice it before but physical RAM is being devoured too
I am running clamd and clamdscan I had already read that this was best practice.
As far as your suggestion of lowering the maxproc setting in master.cf of postfix.
The filter line in master.cf looked like this:
filter unix - n n - - pipe
maxproc for this would be 100 by default right?
So I edit this line to:
filter unix - n n - 25 pipe
right? Less? More?
My last question is about the executable output from perlcc sanitizer.pl
I cd over to the /usr/local/anomy/bin dir then ran perlcc sanitizer.pl
the result was a file in this working directory called a.out that is executable
What do I do with it? rename it like :
copy the original sanitizer.pl to sanitizer.pl.bak, then
mv a.out to sanitizer.pl
I guess this question is worded better like this,
Now that I ran perlcc against sanitizer.pl I need to have filter.sh call this output file instead of the original sanitizer.pl right? Either by renaming this output file or by editing filter.sh to call a.out, right?
-- _______________________________________________ Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free! http://www.net2phone.com/cgi-bin/link.cgi?143