Bug 11431
Summary: | mutt cannot lock NFS mounted mailfiles | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | benjamin-redhat |
Component: | mutt | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-05-16 16:09:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
benjamin-redhat
2000-05-16 03:47:24 UTC
You need to have the nfslock service started on both the client and the server for NFS locking to work correctly. Sorry to come back to you so late, but I partially had to wait for feedback from my administrator. By the way, I think the resolution "NOTABUG" is not correct, because nfslock was not only not started, but also not installed at all, although I have several NFS mounted devices. The problem that I have now is that the server does not run a knfsd, but a user space one (because it had stability problems which the user space one solved, AFAIK), and nfslock seem to only be thought for knfsd. Well, the server administrator refuses to switch back to knfsd. But I guess, it must be possible somehow to "connect" also with a 6.1 system, when a 5.2 system has no problem at all. If I am not wrong, the "solution" of the 5.2. system was that locking did not really lock the stuff. Am I correct? If so, I would be happy with a similar solution for 6.1, because there will be no concurrent accesses. Do you have any suggestions for me? Thank you for your attention. |