Re:procmail: Locking "tmp.lock" (smartlist)

At 2:27 PM -0400 7/13/05, Kim Ridenour is rumored to have typed:

> I have forms that automatically process subscribe/unsubscribe requests using
> x-command.

   Bad form. Send a mail to the list; this allows the confirmation routines
to function. Using automated X-Commands to subscribe people allow your list
to be used for revenge spamming. (Because it hasn't happened yet doesn't mean
it won't; I strongly urge you to think long and hard befonre continuing this
practice.)

(re: tmp.lock)
> Can anybody tell me what the cause and cure are for this?

   There is nothing wrong with this; it's by design. procmail is processing
recipies within SmartList which create a temporary lock file with that name,
so other procmail processes do not muck with the file locked until this
process is finished with it.

   Both rc.request and rc.submit use tmp.lock for the tempoorary lockfile
name (use pico or joe to read through the files, and you'll come across the
recipies which use it). If you turn verbose on you'll see the variable
assignment as well, at least in rc.request. Whatever caused you to think this
non-problem needed a "cure?"

         Charlie