#28: OpenOffice.org 2.0.x file locking and NFS -----------------------------+---------------------------------------------- Id: 28 | Status: new Component: ports | Modified: Thu Dec 22 21:46:29 2005 Severity: normal | Milestone: Priority: normal | Version: 2.0 Owner: sip@varlock.com | Reporter: jdolan -----------------------------+---------------------------------------------- OOo 2.0.x now uses file locking by default, which is kindof nice, but does not currently work with CRUX's nfs ports, even when lockd is running on both client and server machines. Others (Debain) users have noticed the same behaviour. Some report limited success in reading/writing files over NFS in OOo by downgrading their NFS server's protocol to version2, but this is an undesirable solution for one application. Another option is to disable file locking via the soffice startup script, as this was the default in OOo 1.x: --- /usr/bin/soffice 2005-10-15 10:02:19.000000000 -0400 +++ soffice 2005-12-22 15:38:44.000000000 -0500 @@ -35,13 +35,13 @@ #************************************************************************* # -# STAR_PROFILE_LOCKING_DISABLED=1 -# export STAR_PROFILE_LOCKING_DISABLED +STAR_PROFILE_LOCKING_DISABLED=1 +export STAR_PROFILE_LOCKING_DISABLED # # file locking now enabled by default SAL_ENABLE_FILE_LOCKING=1 -export SAL_ENABLE_FILE_LOCKING +#export SAL_ENABLE_FILE_LOCKING # the following test is needed on Linux PPC with IBM j2sdk142 if [ `uname -s` = "Linux" -a "`uname -m`" = "ppc" ] ; then See http://www.openoffice.org/issues/show_bug.cgi?id=54586 -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/28> CRUX <http://crux.nu/> CRUX