On Fri, Nov 26, 1999 at 04:20:37PM +0100, Paulo Jan wrote:
You've misunderstood the setlock manpage. After setlock's child
exits, the lock on the seriallock file does indeed disappear,
but the file is not removed. This makes sense, because it will
have to be created again soon, so why waste resources removing it?
If you want to test this, find a seriallock file for which the
maildirserial process has completed, then try to lock it yourself:
setlock -n /var/qmail/autoturn/1.2.3.4/seriallock echo ok
If you get back an "ok", it means the file was not locked, implying
that no maildirserial was running at that time. Otherwise, you'll
get an error message from setlock saying it was unable to lock the file.
> Hi all:
>
> Well, I've got at last serialmail and AutoTURN installed and working,
> following the instruciones in the serialmail package. The only problem
> that I have now is that, after triggering an AutoTURN delivery,
> maildirsmtp locks the proper directory, sends the messages in it
> correctly... but never unlocks the directory (that is, it doesn't delete
> the "seriallock" file that it creates). The line that I use to start
> serialmail in my startup scripts is:
[snip]
--
Anand
