procmail is not able to create lock files on NFS share
This document (3792040) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 10
Situation
Resolution
Additional Information
The problem is that since the kernel 2.6.12, the Linux NFS client simulatesflocklocks using fcntl locks on the server. This works fineunlessa client tries to take both an flock and an fcntl lockon the same file at the same time and expects them both to succeed.
This cannot work with the current Linux NFS implementation as theserver will reject the second lock as it sees a conflict. For localfilesystems, the locks are in separate address spaces, and no conflictis seen.
This affects any kernel since 2.6.12 (which includes SLES10) runningwith any program that tries to get both a flock lock and anfcntllock,which procmail does when compiled with LOCKINGTEST=101, but not whencompiled with LOCKINGTEST=100.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3792040
- Creation Date: 01-Jan-2008
- Modified Date:19-Mar-2021
-
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com