To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54586
                  Issue #:|54586
                  Summary:|Cannot open files via NFS on mis-configured Linux
                          |machines
                Component:|framework
                  Version:|680m124
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|lho
              Reported by:|sb





------- Additional comments from [EMAIL PROTECTED] Wed Sep 14 02:33:20 -0700 
2005 -------
Since issue 29425 is fixed, file locking is enabled in OOo.  On some Linux
machines, the attempt to lock a file accessed via NFS results in an error
(ENOLCK), because the machine is mis-configured in that an NFS lock deamon is
not running (ENOLCK can also occur, whether or not a file is accessed via NFS,
in the---somewhat unlikely---event that "satisfying the lock
or unlock request would result in the number of locked regions in the system
exceeding a system-imposed limit" [susv3]).

In OOo, this leads to a cryptic error box "General input/output error while
accessing ..." and failure to open a file via NFS.

There are at least five choices to handle this problem:
1  Disable file locking again.  See issue 29425 for why it was enabled (involved
developer: obr).
2  Blame the mis-configured machines and do nothing (no developer involved).
3  Handle ENOLCK in the OOo code by presenting a more appropriate error message
(possibly including a hint that the problem might be a mis-configured Linux
machine), but still refusing to open the file (involved developer: abi).
4  Handle ENOLCK in the OOo code by presenting a warning message that file
locking did not work for some reason, and opening the file read-only (involved
developer: abi).
5  Handle ENOLCK in the OOo code by presenting a warning message that file
locking did not work for some reason, and opening the file read/write, but
unlocked (involved developers: abi, obr).
In each case, an additional step might be to document the problem of
mis-configured Linux machines in the readme or similar.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to