nfs locking (was: Re: OOO 2.0 compiles but doesn't work properly)

[Daniel O'Connor]

On Fri, 2 Dec 2005 02:19, Gerrit Kühn wrote:
> Yes, I see... the problem seems so be that you have to run lockd and statd
> to get ooo running on nfs. The machine where everything's working fine is
> running 5.4 with statd and lockd. The machine with the problems is running
> 6.0 and didn't have statd and lockd activated.
> However, activating them (and rebooting) didn't solve the problem here.
> That's why I'm taking this over to -stable mailing list:

You can get OOo to not do locking.

Edit this file..
/usr/local/openoffice.org2.0.RC3/program/soffice

and put a # in front of these 2 lines
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING


-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051202/eba1a384/attachment.bin