[Dovecot] 1.0alpha3: fcntl() complaints?

[Timo Sirainen]

On Mon, 2005-09-26 at 12:55 -0400, Jeff A. Earickson wrote:
> Hi,
> 
> Since installing 1.0alpha3 this morning, I've seen this
> syslog complaint a few times.  Anything to worry about?
> A "server too busy" issue?
> 
> imap(user): fcntl() failed with mbox file /var/mail/user: 
> Resource temporarily unavailable

Hmm.. I just recently changed that code to write error message if it
happens. In 1.0-stable it's silently ignored. But I'm not really sure
why it would happen. I don't think it should happen as long as I'm
trying to lock using F_SETLKW (waiting the lock) instead of F_SETLK (try
locking).

F_SETLK is used when unlocking the file. But why would unlocking fail?
Or maybe it does with NFS lockd?

Linux's fcntl() man page doesn't talk about F_SETLK explicitly, but I'd
think that's what it means:

       EACCES or EAGAIN
              Operation is prohibited by locks held by other  processes.   Or,
              operation  is prohibited because the file has been memory-mapped
              by another process.

Solaris's man page says it only happens with F_SETLK. UNIX98 says the same.

Maybe I should just change it to be ignored again.. Would be nice to
know what the cause is though.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20050927/61854474/attachment.pgp