Hi,
We are running imapd.2004a on redhat AS3. Some users found that they could not delete messages in their mbox. I found that this is caused by the old imapd process, which does not work but does not go away. It still exclusively opens the mbox file which makes other processes unable to access it. I suspect this is a mbox locking problem.
I just read a document about the mbox locking. According th the document, if the softwares, which are dealing with mbox, are using multiple common locking mechanism, they must be used in the same order to avoid deadlocks.
We are running postfix and procmail on our uw-imap servers. I checked the locking mechanism used in postfix and procmail. They are in different order. I don't know how to check what locking uw-imap is using such that I can identify which one mismatches. I wonder if anybody can help?
Kai Wang University of Calgary _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
