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] Sun Oct 16 09:22:03 -0700 
2005 -------
On a machine with NFS file locking working (Fedora Core 1, kernel 2.4.29) and
the default OOo setup (SAL_ENABLE_FILE_LOCKING=1), I had a crash in OOo2.0rc3
while configuring the tool bar. I had to "killall -9 soffice.bin" from the
console to recover, as X was wedged and "killall soffice.bin" was not
successful. When OOo terminated, it took X with it (X server restarted). After
logging in and restarting OOo, I allowed OOo to recover the open files as
requested and sent the error report. The two open documents were reported as
successfully recovered, but I was only able to open them in "read-only" mode.
These documents were saved in my home directory, which is NFS-mounted from
another machine. Copying the documents to a new file and opening the copy worked
fine, so suspecting an NFS lock issue, I closed OOo, commented out the
SAL_ENABLE_FILE_LOCKING lines in the soffice script, restarted OOo, and was able
to open the original recovered documents without problems. Will nfs file locks
time out eventually and allow opening without disabling OOo's nfs file locking?
Or does the nfs filesystem have to be remounted or nfs processes restarted in
order to clear the file locks? Either way it seems cumbersome, especially when
the documents were successfully recovered after the OOo crash. For the time
being I am leaving nfs file locking disabled.



---------------------------------------------------------------------
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