On Wed, 30 Nov 2005 10:29:02 -0500 Robert Huff <[EMAIL PROTECTED]> wrote
about OOO 2.0 compiles but doesn't work properly:
RH> > The home directory is coming from a nfs-server, so the user-setup
RH> > should be identical. I already tried to delete .openoffice.org2,
RH> > but that didn't help ei
Hi,
Am Donnerstag, 1. Dezember 2005 16:49 schrieb Gerrit Kühn:
> I've got a FreeBSD 6.0 NFS client here, which is connected to
> a FreeBSD 4.10-Server. Both sides are running statd and lockd,
> but processes requesting locks (kdm in the first place after
> booting here) get stuck in the state "loc
On Thu, 01 Dec 2005 16:49:55 +0100, Gerrit Kühn
<[EMAIL PROTECTED]> wrote:
On Wed, 30 Nov 2005 10:29:02 -0500 Robert Huff <[EMAIL PROTECTED]> wrote
about OOO 2.0 compiles but doesn't work properly:
RH> > The home directory is coming from a nfs-server, so the user-setup
RH> > should be ident
Hello,
> >RH> Yes - check the archives. There was at least one other person
> >RH> reporting problems with OpenOffice+NFS.
> >
> >Yes, I see... the problem seems so be that you have to run lockd and
> >statd
> >to get ooo running on nfs.
Same here:
NFS server 5.4-REL, client 5.4p8, no lockd
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 st
On Fri, 02 Dec 2005 01:31:43 +0100, Daniel O'Connor
<[EMAIL PROTECTED]> 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
