[ooo-build] [Issue 113330] oowriter cannot open documents on nfs shares

[p92 at openoffice.org]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113330





------- Additional comments from p92 at openoffice.org Fri Jul 23 11:48:31 +0000 2010 -------
My home is on a local dir. Documents are on a NFS mounted dir.
Btw what do you mean by "locking enabled & working" ? How do I check that ?

my NFS entry in fstab is :
synology:/volume1/PC   /mnt/pc   nfs _netdev,nouser,auto,rw,dev,exec,suid  0  0 

Mount:
synology:/volume1/PC on /mnt/pc type nfs (rw,addr=192.168.0.2)


I have investigated more and found that if I launch openoffice with the script
oowriter locks on the splash screen :

$ /usr/lib/openoffice/program/soffice -writer "/mnt/pc/proposition de mise en
oeuvre de pci-pra.odt" 
+ test -z /home/pascal
+ FILE_LOCKING=auto
+ OPENGL_SUPPORT=no
+ [ -f /etc/openoffice/soffice.sh ]
+ . /etc/openoffice/soffice.sh
+ FILE_LOCKING=auto
+ OPENGL_SUPPORT=no
+ [ -z  ]
+ home_on_nfs -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt
+ stat -f -c %T /home/pascal
+ return 1
+ [ 1 = 0 ]
+ file_on_nfs -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt
+ continue
+ [ -f /mnt/pc/proposition de mise en oeuvre de pci-pra.odt ]
+ stat -f -c %T /mnt/pc/proposition de mise en oeuvre de pci-pra.odt
+ return 0
+ [ 0 = 0 ]
+ SAL_ENABLE_FILE_LOCKING=0
+ export SAL_ENABLE_FILE_LOCKING
+ STAR_ENABLE_FILE_LOCKING=0
+ export STAR_ENABLE_FILE_LOCKING
+ [ -z  ]
+ SAL_NOOPENGL=true
+ export SAL_NOOPENGL
+ [ LINUX = LINUX -a INTEL = POWERPC ]
+ pwd
+ sd_cwd=/home/pascal
+ [ -h /usr/lib/openoffice/program/soffice ]
+ dirname /usr/lib/openoffice/program/soffice
+ cd /usr/lib/openoffice/program
+ pwd
+ sd_prog=/usr/lib/openoffice/program
+ cd /home/pascal
+ basename /usr/lib/openoffice/program/soffice
+ sd_binary=soffice.bin
+ sd_pagein_args=@pagein-common
+ sd_pagein_args=@pagein-common @pagein-writer
+ break
+ /usr/lib/openoffice/program/../basis-link/program/pagein
-L/usr/lib/openoffice/program/../basis-link/program @pagein-common @pagein-writer
+ [ -x /usr/lib/openoffice/program/../basis-link/ure-link/bin/javaldx ]
+ /usr/lib/openoffice/program/../basis-link/ure-link/bin/javaldx
-env:INIFILENAME=vnd.sun.star.pathname:/usr/lib/openoffice/program/redirectrc
+
my_path=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64
+ [ -n
/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64
]
+
LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64
+ export LD_LIBRARY_PATH
+ unset XENVIRONMENT
+ [ -f /etc/adabasrc ]
+
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
+ export PATH
+ PYTHONPATH=/usr/lib/openoffice/program/../basis-link/program
+ export PYTHONPATH
+ [ -writer = -nologo -o -writer = -no-oosplash ]
+ [ /mnt/pc/proposition = -nologo -o /mnt/pc/proposition = -no-oosplash ]
+ [ de = -nologo -o de = -no-oosplash ]
+ [ mise = -nologo -o mise = -no-oosplash ]
+ [ en = -nologo -o en = -no-oosplash ]
+ [ oeuvre = -nologo -o oeuvre = -no-oosplash ]
+ [ de = -nologo -o de = -no-oosplash ]
+ [ pci-pra.odt = -nologo -o pci-pra.odt = -no-oosplash ]
+ [ soffice.bin = soffice.bin -a -x /usr/lib/openoffice/program/oosplash.bin ]
+ [  != y ]
+ sd_binary=oosplash.bin
+ trap kill -9 $! TERM
+ wait 31713
+ /usr/lib/openoffice/program/oosplash.bin -writer /mnt/pc/proposition de mise
en oeuvre de pci-pra.odt

But if I launch oowriter directly from /usr/lib/openoffice/program/oosplash.bin
-writer "/mnt/pc/proposition de mise en oeuvre de pci-pra.odt"

I experience no lock and oowriter gui is even A LOT MORE responsive than usual
especially when in the file selector where it is usually very very slow to
display directory contents !




---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification