Question about lmtp.lock

[Derrick J Brashear]

On Mon, 13 Dec 2004, David G Mcmurtrie wrote:

> We've installed cyrus imapd 2.1.17 on a 4-node Veritas cluster and we're
> now testing it.  Our /var/imap filesystem is on a clustered filesystem.
>
> We noticed that all of the lmtpd processes are just sitting in a blocking
> fcntl() call waiting for a lock on /var/imap/socket/lmtp.lock.  When we
> run this in a clustered environment, each lmtpd is consuming CPU resources
> while blocking.  In a non-clustered ufs environment they do not.
>
> Is there any reason that the lmtpd processes need to be serialized across
> different nodes in a cluster?  If not, we'll just write these lock files
> to local ufs space on each cluster node.

i assume each node has its own address, and therefore you want the lmtp 
locks to be per-node.

> While I'm on the subject, what is the purpose of
> /var/imap/socket/imap.lock?

which imapd gets to accept(). same deal, different daemon. it's all done 
in master's service routines.

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html