To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54586
------- Additional comments from [EMAIL PROTECTED] Fri Dec 9 07:51:34 -0800 2005 ------- My target for this issue is, like proposed by SB, to handle the following: 1. On certain Linux machines, file locking is known to fail due to the NFS lock demon not running. 2. Disabling file locking rises other problems, see issue 29425 The following has to be considered: - Report: Welcome dialog appears every time - Report: AutoRecovery restores documents read-only Recommended solution: (Tend to use #4, but maybe we need possibility to open/read write) #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). or #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. Notes: We have to inform the user when loading the document. --------------------------------------------------------------------- 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]
