Date: Sat, 6 May 2006 22:04:42 +0200 From: dick hoogendijk <dick@nagual.st> To: fbsdq <freebsd-questions@freebsd.org> Subject: Re: i/o error OOo-2.0.2 NFS Message-ID: <20060506220442.3948eb84.dick@nagual.st> In-Reply-To: <20060505152418.26d70422.wmoran@collaborativefusion.com> References: <20060505085536.GA812@arwen.nagual.st> <20060505125147.20418bbd@localhost> <20060505194900.231673d1.dick@nagual.st> <20060505152418.26d70422.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 May 2006 15:24:18 -0400 Bill Moran <wmoran@collaborativefusion.com> wrote: > 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. OOo2 runs OK. Opening files from a NFS server is OK too. I run rpc.lockd and rpc.statd on *both* the server and the client now and OOo2 gives no more errors. But, in the docs I read about a var setting: SAL_ENABLE_FILE_LOCKING=0 Is this a more preferable way of getting rid of the I/O errors mentioned earlier? I searched the archives butam not sure about the right way. Advice please.. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 ++ The Power to Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060506220442.3948eb84.dick>