On 1999-11-16 18:09:17 -0600, David DeSimone wrote: > If you are *certain* that every mail-handling program at your site uses > the same dot-locking mechanism, you can reconfigure Mutt with > --disable-fcntl, and then you won't have this problem. But if you're > wrong, and there is some program that does try to perform fcntl-locks as > the only method to prevent synchronization problems, then the two > programs can collide and trash the folder if they access it at the same > time. When doing this, make sure you disable caching on the NFS client. -- http://www.guug.de/~roessler/
- fcntl: No locks available (errno = 37) Dan Lipofsky
- Re: fcntl: No locks available (errno = 37) Lalo Martins
- Re: fcntl: No locks available (errno = 37) Lalo Martins
- Re: fcntl: No locks available (errno = 37) Mikko Hänninen
- Re: fcntl: No locks available (errno = 37) Lalo Martins
- Re: fcntl: No locks available (errno = 3... David DeSimone
- Re: fcntl: No locks available (errn... Thomas Roessler
- Re: fcntl: No locks available (errn... Marius Gedminas
- Re: fcntl: No locks available (... David DeSimone
- Re: fcntl: No locks available (errno = 37) Stephan Seitz
- Re: fcntl: No locks available (errno = 37) Bill Nottingham
- Re: fcntl: No locks available (errno = 37) Joshua Rodman
- Re: fcntl: No locks available (errno = 37) Dirk Pirschel
- Re: fcntl: No locks available (errno = 37) Roland Rosenfeld
- Re: fcntl: No locks available (errno = 3... Mikko Hänninen
- Re: fcntl: No locks available (errno = 37) Roland Rosenfeld
- Re: fcntl: No locks available (errno = 37) Dan Lipofsky