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

Ronald Klop ronald-freebsd8 at klop.yi.org
Fri Dec 2 00:49:24 GMT 2005


On Fri, 02 Dec 2005 01:31:43 +0100, Daniel O'Connor  
<doconnor at gsoft.com.au> wrote:

> 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

Eclipse needs/uses it. Firefox needs/uses it. Why change the applications  
if their is a non-working feature? btw: A better _workaround_ is to use  
the option -L of mount_nfs.

Sorry, I can't fix this, but I can provide some log output if anybody is  
interested.

-- 
  Ronald Klop
  Amsterdam, The Netherlands


More information about the freebsd-stable mailing list