First Last Prev Next    This bug is not in your last search results.
Bug 108257 - oo and loocking over nfs
oo and loocking over nfs
Status: CLOSED CURRENTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: openoffice.org (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2003-10-28 14:11 EST by ae
Modified: 2007-04-18 12:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-27 11:45:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description ae 2003-10-28 14:11:07 EST 
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):
1.1.0-2

How reproducible:
always

Steps to Reproduce:
1. xterm
2. $ ooffice
3.
    
Actual results:
endless (?) delay, no visible result

Expected results:
ooffice app opens

Additional info:
1.1beta is OK.
Dist is redhat 9 with patches to date, two processor.
Comment 1 Dan Williams 2004-02-10 15:05:08 EST 
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' ?
Comment 2 Dan Williams 2004-02-27 11:45:10 EST 
Please try current OOo 1.1.0, and reopen if problem still occurs
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.