procmail
[Top] [All Lists]

Re: procmail: Extraneous locallockfile ignored

2002-02-06 14:03:44
First off.  Thanks for all the help.  I'm starting to get to the bottom
of this.  (I think.)

I set VERBOSE=on, and then ran some test messages and had some colleauges
send some test messages.  Here's the end of what happened.

From timh  Wed Feb  6 15:24:56 2002
 Subject: [ayoungs98(_at_)hotmail(_dot_)com: Pink Samuri Bunny]
  Folder: /var/spool/mail/timh                                             1435
procmail: Unlocking "/home/timh/mail/.lockmail"


It runts through a whole mess of stuff since my ~/.procmailrc is like 450 lines
long, and then ends there.  When I see that, that's a good thing I'm assuming?

that means that it created the lock file, found a match, then removed the lock
file.  Is that correct?  Or am I still not grasping this?  (Long rough day, it
is very well possible!)

So I need to find out what message is creating the lock file, and then nore 
removing it?  Am I on the right path now?

Again, thanks for the help!  It's greatly appreciated!
tdh

p.s.
The uptime in signature was just kewl when I first saw/set it up.  I've
since forgot it was even there.  At one point I even boasted an uptime
of like 160 days.  Recent power outages, server rebuild wiped that 
clean though.
-- 
  --------------------------------------------------------------------
  T. Holmes  |  UNIXTECHS.org  |  tim(_at_)unixtechs(_dot_)org  |  UIN:  
17021091
  --------------------------------------------------------------------
 | At 13:07 2002-02-06 -0500, Tim Holmes wrote:
 | >I keep getting these line in my procmail.log, and I'm not sure why.
 | >
 | >procmail: Extraneous locallockfile ignored
 | >procmail: Extraneous locallockfile ignored
 | 
 | >What causes those locallockfile messages that litter my log?
 | 
 | Try searching the list archives.  Also, try enabling VERBOSE logging, which 
 | would allow you to pair up these errors to the specific recipes which are 
 | triggering them.  Chances are you have something like:
 | 
 | :0:
 | * somecondition
 | {
 |         :0:
 |         file
 | }
 | 
 | 
 | Or something more elaborate, but the idea is that you have the lockfile at 
 | the outer brace level and it isn't needed except when you're outputting to 
 | a file (or when running certain scripts which you don't want to have 
 | running concurrently).
 | 
 | >This doesn't always happen either.  Sometimes, if a number of emails come
 | >down at the same time, I see that.  But other times, when no mail has come
 | >in for a while, I don't.  What's the deal here?
 | 
 | If the mail you're filtering doesn't travel clear through your rulesets, or 
 | trigger the rule which has the extraneous locallockfile, then you're not 
 | going to see the warnings, are you?
 | 
 | [snip - is your uptime really something that needs to be in a .sig?]
 | 
 | ---
 |  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(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
 | http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
  ------------------------------------------------------------------ 
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>