Nathan Phillip Brink writes:
I had trouble using a courier-imapd account on my computer after it underwent a reboot. Whenever the client tried accessing the trash folder, courier-imap would sit waiting for a lock to be broken.
I do not believe that there's any code in Courier-IMAP that waits for any locks to be broken.
Is it possible for a future version of courier-imapd to correct such a problem itself by recognizing that /proc/$PID/exe != /proc/self/exe? I
If Courier-IMAP actually had any code that checked /proc/$PID/exe, then perhaps yes, but I do not believe there's any code that does that. Especially since /proc/$PID/exe is a Linux/Solaris aspect, and Courier-IMAP runs just fine on other platforms, too.
Also, is this the place to report bugs?
Well, yes, if this was an actual bug.
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.
pgpV5OarK6NCS.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
