On Mon, 13 Oct 2003 13:46:10 -0700, Vicki Brown <[EMAIL PROTECTED]> posted to gmane.mail.spam.spamassassin.general: > We call Spam Assassin from procmail (and call procmail from .forward). > Out .procmailrc contains > > :0 fw:sa_foo.lock > * < 256000 > | /usr/local/bin/spamassassin > > We're seeing steadily increasing procmail processes for one user (of several > who use Spam Assassin and procmail) > > We're also seeing errors in the procmail log file for this user: > > procmail: Rescue of unfiltered data succeeded > procmail: Terminating prematurely whilst waiting for lockfile "sa_rdm.lock" > procmail: Terminating prematurely whilst waiting for lockfile "sa_rdm.lock"
These are an indication that the first instance of Procmail to grab the lock will keep it for so long that other instances give up on waiting for their turn. If you read what it says in procmailrc.example, this is (apparently) done on purpose this way so as to "keep load down", but it's by no means the only way to skin a cat. Probably the most straightforward change would be to install spamd and call spamc from Procmail, without locking. /* era */ -- The email address era the contact information Just for kicks, imagine at iki dot fi is heavily link on my home page at what it's like to get spam filtered. If you <http://www.iki.fi/era/> 500 pieces of spam for want to reach me, see instead. each wanted message. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
