Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Nov 2005 10:08:49 -0500
From:      Bill Moran <wmoran@potentialtech.com>
To:        Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
Cc:        questions@freebsd.org
Subject:   Re: OpenOffice 2 unable to work with files over NFS
Message-ID:  <20051121100849.738eeae8.wmoran@potentialtech.com>
In-Reply-To: <443blv0ygm.fsf@be-well.ilk.org>
References:  <20051117160615.0e9af6de.wmoran@potentialtech.com> <443blv0ygm.fsf@be-well.ilk.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote:

> Bill Moran <wmoran@potentialtech.com> writes:
> 
> > uname -a
> > FreeBSD bolivia.potentialtech.com 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #1: Fri May 27 01:08:00 EDT 2005     wmoran@bolivia.potentialtech.com:/usr/obj/usr/src/sys/WORKING  i386
> > 
> > open pkg_info | grep office
> > openoffice.org-2.0.0_1 Integrated wordprocessor/dbase/spreadsheet/drawing/chart/
> > 
> > OO works fine, unless I try to connect to a document over NFS.  Then all goes
> > badly.  I consistenly get a "general input/output error while accessing
> > <filename>"  This occurs when trying to open previously created .sxc
> > and .odt docs, as well as when trying to create new documents.  I'm having
> > the exact same problem on a laptop, which is nearly the same FreeBSD setup.
> > 
> > OO 1.x has worked fine on this setup for quite a while.  I recently upgrade
> > to OO 2 and *boom* can't work off the server.
> > 
> > If I copy any of these files from the server to my local HDD, all is well.
> > I chmoded the files to 777, but it doesn't make any difference.  I have
> > never had any other problems with this NFS server prior to this (and
> > I don't at this time, either).  The file server is still FreeBSD 4.
> > 
> > I'm going to try to do some NFS debugging, but I'm not an NFS expert by
> > any stretch of the imagination, so I thought I'd a) first see if anyone
> > else was familiar with this issue b) see if anyone had any advice on
> > how to proceed with debugging.
> 
> Enable RPC statd and lockd.
> 
> rc.conf:
> rpc_lockd_enable="YES"
> rpc_statd_enable="YES"

Yup.  That fixed it.

That's why I ask questions on this list - because you guys are wicked smart.

Thanks.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051121100849.738eeae8.wmoran>