Apache OpenOffice (AOO) Bugzilla – Issue 26086
workstation installation on client machine didn't work using symbolic links and NFS shares
Last modified: 2004-03-08 13:29:12 UTC
Hi, I've installed OpenOffice 1.1.0 on our central Linux application server. The application is intended to be loaded through NFS on various Linux desktops. A very nice way to install applications once and have all desktops see the new version without having to run from desktop to desktop. It worked well with OpenOffice 1.0.1. Installation on the server with 'install --interactive': Worked perfect. Then I tried to run the 'setup' program of the newly installed office from a desktop with '/com/office/open-1.1.0/setup': I got and error message with: "Important program files were not found. Installation set may be damaged." How the things are installed on the server: In /com/office/open-1.1.0, with /com being a symlink /com -> /raid5/com/. How the things are set up on the desktops: In /com/office/open-1.1.0, with /com being a symlink /com -> /mnt/nfs/com/, and /mnt/nfs/com being the NFS mount point. In the setup.log file on the server I noticed that there were substitutes being made, but all were accurate with the /com/office/open-1.1.0 prefix. During installation I noticed that when I was asked for installation path, the program was trying to "guess" non-symlinked paths if I used the point-and-click interface, but I entered the paths manually to get "/com/office/open-1.1.0".
CCed mci
Hi schutzm, thanks for using and supporting OpenOffice... I tried the following with OOo1.0.1, OOo1.1.0, OOo1.1.1b. I installed OOo into a symlinked directory on a nfs share as a network installation and as a workstation installation into a symlinked directory on a nfs share. All worked as expected... Please tell us: - which distribution do you use? - where did you get OOo from? - Did you update the old installation or did you do a complete new install?
changed summary from "NFS: Unusable installation on client machine" set to worksforme
.
Hi mci, Thanks for your quick answer. To your questions: - which distribution do you use? Caldera 3.1.1 (please no flame, decision was made long before it became SCO). Linux kernel 2.4.13 glibc 2.2.4 Server and workstation run the same kernel, libc, NFS. - where did you get OOo from? http://download.openoffice.org/1.1.0/index.html Both 1.0.1 and 1.1.0 were downloaded starting with http://www.openoffice.org and following the links to the download. - Did you update the old installation or did you do a complete new install? I made a new install. /com/office/open-1.0.1 still has the 1.0.1 installation /com/office/open-1.1.0 has the new 1.1.0 installation I've just tried the following: Opened the NFS export to 'root' for the workstations (option "no_root_squash"). Installed OO-1.1.0 from a workstation through NFS instead of "natively" on the server. The result now looks the same as issue 19339. Registration troubles with components. Since our Linux distribution doesn't support the NFS option "link_relative" I think it will be a good reason to upgrade to something newer... and non SCO :-) Thanks again for your answer. Your wording pointed to the right way to test: install through NFS, not "natively" on the server. I think the issue can be closed. Maybe something to add to minimum Linux system requirements (kernel, NFS versions). I let you judge.
Hi schutzm, thanks for your response... Please submit an enhancement issue to add information about nfs to system requirements. I'll close this Issue now...