> On 2005-02-08, 12:37:34 (-0500), Derrick Webber wrote:
> > Note that perlcc is still experimental... you might want to run a
> > few e-mails through the binary by hand (or use the test script
> > provided with anomy) to verify it actually runs correctly.
> For "posterity", it would also be interesting if you'd post to the
> list the results of this experiment: does it work and does it
> noticably improve performance?
> Bjarni Rúnar Einarsson
as of right now, its seems that running the spamd / spamc combo has taken care of the problem.
i tried to use the a.out file output from running sanitizer.pl through perlcc, but it was not working, but that may have been a permissions thing (i had to wait until after hours to edit config and it got late so instead of fighting it i reverted to calling the straight sanitizer.pl because i knew it worked :)
i may try again to get it running, but for right now things are running a lot better what was taking an hour or more yesterday is now running around a minute
CPU use will still spike as i have been watching it on and off all day, but before i made the changes last night it was pinned at 95 to 100% for almost a week
thank you for the input,
and if i do get the perlcc ver of sanitizer running i will post all results
-- _______________________________________________ Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free! http://www.net2phone.com/cgi-bin/link.cgi?143