Re: Lock failure

Professional Software Engineering yazmış:

At 15:06 2007-11-30 +0200, Tolga wrote:
  

Why do I keep getting the below error? I just noticed that it only
happens when a mail arrives at the main folder.
    

This looks like the same thing you posted about previously, when you also 
didn't post the RECIPE which corresponded to the logfile entries.  I prefer 
to use my psychic powers to predict lottery numbers, not figure out what 
someone's recipe was.
  

Sorry, below is all of my recipe:

DEFAULT=/var/mail/$LOGNAME
MAILDIR = /var/mail/folders/$LOGNAME
:0
* ^Sender:(_dot_)*owner-postfix-users(_at_)postfix(_dot_)org
postfix
:0
* ^Subject:.*Postfix log summary of (to|yester)day
pflogsumm
:0
* ^Subject:.*\[mrtg\]*
mrtg
:0
* ^Subject:.*Logwatch for ozses.net \(Linux\)
LogWatch
:0
* ^Sender:(_dot_)*procmail-bounces(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
procmail
:0
* ^Sender:(_dot_)*imp-bounces(_at_)lists(_dot_)horde(_dot_)org
horde-imp
:0
* ^From:(_dot_)*fatura(_at_)smileadsl(_dot_)com
! tatlimcik(_at_)hotmail(_dot_)com
:0
* ^From:.*gokce*
Gokce
:0
* ^Subject:.*\[SPAM\]*
SPAM

If you use the 'f' flag on a recipe whose action is to SAVE THE MESSAGE TO 
A FILE, then the flag is meaningless, because you're not PIPING THE MESSAGE 
TO A FILTER, which is what the f flag is for (to differentiate from piping 
the message to a program which eventually delivers the message, or can be 
considered to have done so).

  

procmail: Extraneous filter-flag ignored
procmail: Locking "/var/mail/tolga.lock"
procmail: Error while writing to "/var/mail/_CDH.4oAUHB.ozses.net"
procmail: Lock failure on "/var/mail/tolga.lock"
    

The write and lock failures aren't unexpected - it appears you're trying to 
create files in /var/mail - are your permissions set such that you SHOULD 
be able to do that?
  

It doesn't happen when mails go into folders.

procmail: Assigning "LASTFOLDER=/var/mail/tolga"
procmail: Opening "/var/mail/tolga"
procmail: Acquiring kernel-lock
    

For your own MAILBOX however, you should have write perms, which is why 
this works.

  

--
    

[snip]

Wow, a 23 line sigfile.  Once upon a time, people limited themselves to 2 
to 4 lines or so.  Much more than that turns a message into borderline spam.

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.

____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
  

-- 
To code the impossible code,		This is my quest --
To bring up a virgin machine,		To debug that code,
To pop out of endless recursion,	No matter how hopeless,
To grok what appears on the screen,	No matter the load,
					To write those routines
To right the unrightable bug,		Without question or pause,
To endlessly twiddle and thrash,	To be willing to hack FORTRAN IV
To mount the unmountable magtape,	For a heavenly cause.
To stop the unstoppable crash!		And I know if I'll only be true
					To this glorious quest,
And the queue will be better for this,	That my code will run CUSPy and calm,
That one man, scorned and		When it's put to the test.
	destined to lose,
Still strove with his last allocation
To scrap the unscrappable kludge!
		-- To "The Impossible Dream", from Man of La Mancha

____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail