On Tuesday 09 November 2004 20:54, Dylan wrote:
On Monday 08 Nov 2004 22:17 pm, Anders Johansson wrote:
On Monday 08 November 2004 22:56, Dylan wrote:
Actually, that is not what I meant: OOo cannot reside on an nfs export for execution 'across the network' - each machine needs its own copy, then after the user has done their own 'local' install they can use it on any machine.
That isn't true. It is perfectly possible to have openoffice installed on a server and run it from other machines over an nfs share. I'm doing it right now
You may want to look at http://user-faq.openoffice.org/faq/ar01s04.html#id2811506 though
OK - I've got it installed on a server and it DOES work - sorry for the confusion) except that I have a different problem. Firstly - the link_relative option mentioned in the faq is rejected by exportfs and apropos says 'nothing appropriate.'
Yeah, that seems to be an obsolete option, I didn't use it myself, I just found it in the FAQ and thought it could be a potential stumbling block
Now, since the install directory on the server must be one which is exported, I installed it to /srv/nfs/office - so far so good. This directory is mounted by clients at /opt/remote_apps/office . Unfortunately, this means that all the references to the install directory which OOo creates refer to the wrong place! Any suggestions? (short of installing to /opt/remote_apps/office on the server which I would prefer not to do)
hm, I took an existing suse install in /usr/lib/ooo-1.1/ and moved it to /usr/local/ooo-1.1, /usr/local is exported and mounted on clients as /mnt/server, then on the clients which did not have ooo installed I ran /mnt/server/ooo-1.1/setup and everything worked fine. No complaints about bad links or anything. Which errors did you see?