Date: Fri, 2 Dec 2005 11:01:43 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-stable@freebsd.org Cc: Gerrit =?iso-8859-1?q?K=FChn?= <gerrit@pmp.uni-hannover.de> Subject: Re: nfs locking (was: Re: OOO 2.0 compiles but doesn't work properly) Message-ID: <200512021101.44391.doconnor@gsoft.com.au> In-Reply-To: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de> References: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1942108.VuNUW46GLn Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 2 Dec 2005 02:19, Gerrit K=FChn 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=3D1 export SAL_ENABLE_FILE_LOCKING =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1942108.VuNUW46GLn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDj5Xw5ZPcIHs/zowRAoQVAJ9kjxJsNlLp85uZBqJDByPCTdfyJwCeNGX4 ca12MIL1eUpdtHl9/gEwjuc= =wC/n -----END PGP SIGNATURE----- --nextPart1942108.VuNUW46GLn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512021101.44391.doconnor>