Date: Fri, 5 May 2006 15:24:18 -0400 From: Bill Moran <wmoran@collaborativefusion.com> To: dick hoogendijk <dick@nagual.st> Cc: freebsd-questions@freebsd.org Subject: Re: i/o error OOo-2.0.2 NFS Message-ID: <20060505152418.26d70422.wmoran@collaborativefusion.com> In-Reply-To: <20060505194900.231673d1.dick@nagual.st> References: <20060505085536.GA812@arwen.nagual.st> <20060505125147.20418bbd@localhost> <20060505194900.231673d1.dick@nagual.st>
next in thread | previous in thread | raw e-mail | index | archive | help
dick hoogendijk <dick@nagual.st> wrote: > On Fri, 5 May 2006 12:51:47 +0200 > Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > > > dick hoogendijk <dick@nagual.st> wrote: > > > > > Yesterday I installed OpenOffice-2.0.2 from (the most recent) > > > ports. It runs very well, but I have an error that I don't > > > understand. > > > > > > Opening a file on my local machine is OK, but when I try to open > > > one on a NFS mounted directory I get an I/O general error and the > > > file is not opened. I run OOo-1.1.5 on the same machine without any > > > problems. Any ideas where (what) to look (for)? > > > > man rpc.lockd (Just a guess, I don't use OpenOffice). > > I don't think so. OOo-1.1.5 opens the (NFS served) file OK. The same > file gets denied by OOo-2.0.2. The only $var is another OOo version ;-) Think so. This is the exact same problem I had when I upgrade from OOo1 to OOo2. Search the archives and you'll see that Fabian is correct and that it solved the problem for me. Apparently, OOo2 is more careful about locking semantics. -- 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?20060505152418.26d70422.wmoran>