Sam Varshavchik wrote:
> Nathan Phillip Brink writes:
>> Also, is this the place to report bugs?
>
> Well, yes, if this was an actual bug.
good.
>
>> Below is an edited shell session of me finding and removing the stale
>> lock:
>>
>> margbr...@ohnopublishing ~/.maildir/.Trash/tmp $ ls -lha
>> ...
>> -rw-r--r-- 1 margbrink margbrink    8 Jul 21 21:00
>> 1248224418.M734712P16152.ohnopublishing.net
>> -rw-r--r-- 1 margbrink margbrink   23 Jul 18 21:19 courier.lock
>>    $ less courier.lock
>> 7892:ohnopublishing.net
>
> Whatever this file is, it wasn't created by Courier-IMAP. Furthermore,
> Courier-IMAP has no problems with concurrent access to the same
> folder, by different instances of the IMAP server, so it has no need
> for any locks of any kind, here.
Then what software names a file ``courier.lock''? And why would removing 
this file cause courier to behave properly afterwards?

I'm sorry so say so, but I don't believe you. I recognize that 
courier-imapd should require no locks (according to the docs), but its 
own manpages say that locks are suggested when enabling the IDLE command 
(which I have done). Maybe my installation of courier-imap (possibly 
modified by Gentoo?) uses a nonstandard value for WATCHDOTLOCK:
./maildir/maildirwatch.h:#define WATCHDOTLOCK   "tmp/courier.lock"

Maybe I stated something unclearly before. Even though the courier.lock 
file I examined earlier pointed to the PID a running dkim-milter 
process, this same PID was being used by a courier-imapd daemon _before_ 
my computer unexpectedly rebooted. I am mostly interested in an 
automatic way of removing locks that get left in the filesystem after an 
unexpected reboot that covers the possibility of the PID being reclaimed 
by a non-courier-imapd process (that may possibly never exit until the 
machine reboots again).

-- 
binki


------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to