I agree with the fact that the lock is not needed on spamc, but I don't
understand why this would produce an error.  There are a lot of individuals
that use the lock with both spamassassin and spamc as a load control.  Is it
possible that by using DROPPRIVS=yes removes the permissions necessary to
create and write to spamassassin.lock?

--Larry


> -----Original Message-----
> From: Pete Hanson [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, November 05, 2003 10:51 PM
> To: Mitchell D. Baker; [EMAIL PROTECTED]
> Subject: Re: [SAtalk] lock problems with SPAMC
> 
> 
> I think you may be putting a lock on the recipe that runs spamc - 
> you don't want to do that.  The only time you need to lock in 
> procmail is when you're writing to a file that might be called by 
> multiple procmail processes at one time.
> 
> So, instead of:
> 
>     :0 fw:
>     | spamc
> 
> you want:
> 
>     :0 fw
>     | spamc
> 
> At 8:41 AM -0500 11/5/03, Mitchell D. Baker wrote:
> >Here is our setup...
> >
> >2 inbound mail servers solaris running sendmail, one primary one 
> >secondary.  Secondary has all users inboxes NFS mounted to 
> the primary 
> >and 4 imap/pop servers.
> >
> >If I crank up spamd/spamc things start to bog down greatly.. I 
> >never see but one spamd/spamc process at a time but my promail's 
> >start to climb...  The global procmailrc file is pretty much the 
> >example from the doc's.. If I add DROPPRIVS=yes to the procmailrc 
> >then I get all lots of message of:
> >
> >procmail: Lock failure on "spamassassin.lock"
> >procmail: Lock failure on "spamassassin.lock"
> >>From [EMAIL PROTECTED]  Wed Nov  5 08:23:18 2003
> >  Subject: RE: Pictures for the grossest picture contest in 
> the Rho Phi
> >   Folder: /var/mail/xxxxxx                                         
> >128795
> >procmail: Lock failure on "spamassassin.lock"
> >procmail: Lock failure on "spamassassin.lock"
> >procmail: Lock failure on "spamassassin.lock"
> >procmail: Lock failure on "spamassassin.lock"
> >procmail: Lock failure on "spamassassin.lock"
> >procmail: Lock failure on "spamassassin.lock"
> >
> >Last bit if info, users home dirs are in AFS space... Where is the 
> >spamassassin.lock file created?  Is there a way to tell if where to 
> >create it?
> >
> >See-ya
> >Mitch
> >
> >-- 
> >/############################################################
> ########/
> >/# Mitchell "Buzz" Baker               "To Infinity And 
> Beyond..."  #/
> >/# Sr. Systems/Security Admin  Rose-Hulman Institute of 
> Technology  #/    
> >/# [EMAIL PROTECTED]            
> www.rose-hulman.edu  #/
> >/#        For PGP Public key, check 
> out www.keyserver.net           #/
> >/############################################################
> ########/



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to