Red Hat Bugzilla – Bug 108257
oo and loocking over nfs
Last modified: 2007-04-18 12:58:50 EDT
Description of problem:
ooffice fails to start for user whose home dir comes from solaris
via nfs/nolock. (The nolock practice began as a workaround for a problem
with wordperfect 8 multiuser.)
OK for user whose home comes from ext3 file system.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. $ ooffice
endless (?) delay, no visible result
ooffice app opens
1.1beta is OK.
Dist is redhat 9 with patches to date, two processor.
This happens because OOo is attempting to lock your ~/.recently-used
file for reading/writing. When OOo freezes, can you check what
programs have that file open using 'lsof' ?
Please try current OOo 1.1.0, and reopen if problem still occurs