Bug 41670
Summary: | Star Office 5.2 can't be used with homes mounted via NFS | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <christina.zeeh> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | ajb, dennis.brylow, otto.paukner |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-06 12:50:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-05-21 19:15:38 UTC
We're using StarOffice 5.2 on NFS mounted home directories (both RH6.2 and RH 7.1) just fine. I've patched StarOffice with updates available from sun... maybe that will help you too. http://supportforum.sun.com/staroffice/patches.html I can confirm this bug: all old rh 6.2 workstations have only some little problems, but RedHat 7.1 with all updates and several kernels from the 2.4 tree can't use StarOffice 5.2 anymore. When I softlink .user52.rdb and the so2-directory to a local disk area, everything runs well. Because the dmfe driver isn't included in the standard rh kernel I always have to recompile the kernel by myself. I even tried the new 2.4.6 and discovered an horrible nondeterministic bug: I copied two files to to an 6.2 NFS-server, two 7.1 clients with 2.4.6 kernel couldn't see the files with ls - although I could get them with cat !!! One Debian system and older rh-versions hadn't a problem to ls these two files. What's going on here? People at my company don't like rh-versions greater than 6.2 because things go worse than better. Where is the solution of the StarOffice problem? It has something to do with NFS and the new kernel, I can definetely confirm that. I found a workaround: Install StarOffice 5.2 remote on a RH 6.2 system with your home NFS-mounted to this remote host, then use StarOffice on the local host with 2.4.x-kernel. This explains the comment above. Well, the previous workaround will work fine unless the user decides to do something in Preferences. Then Star Office will try to write to the configuration file(s) and corrupt them and we have the same problem again. The only working workaround I see at the moment is a wrapper script that does the following: - check if configuration files exist in the user's home (meaning Star Office has already been started and installed), if not, give the user default configuration files created by a local "dummy" user - copy the configuration files to a directory in /tmptmp (or any other local, non-NFS partition) - set $HOME to this directory - start Star Office - when Star Office has finished, copy the configuration back to the user's home and reset $HOME Seems to have gone away with the 2.4.9 kernel upgrade. This may be a duplicate of bugid #52652. |