Hi all,

just installed OO 3.01 for Mac PPC and found a similar issue that I
had in earlier versions:
Opening a file from a mounted NFS share works without a problem.
Saving the file causes an error message.
It first of all looks good the bar at the bottom says "Saving
document" and the progress bar moves from left to the right.
Then an error window opens "Error while saving <document name> general
Input / Output error during access to <path to doc on NFS
share>/<document name>"
Clicking on OK gives the same error message again, clicking again on
OK gives a third error message saying " Error: generel I/O error"
I have translated the error message from German so sorry if this is
not the fully correct message.
The Mac is running OS X 10.5.6 (most actual version)
NFS server is running on FreeBSD 4.11
I for sure tried different files and file types and also different shares.
Just to make sure: This is NOT a general access problem with NFS!

Any application on the Mac and I really mean any, including iTunes,
all document processing applications like for example NeoOffice or
simple text edit, ANY can access these shares and open, edit, and save
files there, but OpenOffice.
I already had the same issue with the X11 version of Open Office,
removed it for this reason and went back to NeoOffice.
As I really would prefer to use Open Office I tried it again and found
the same issue.
Searching for this behavior on www.openoffice.org only shows
information about a variable $SAL_ENABLE_FILE_LOCKING that seems not
to exist anymore (at least I can't find the mentioned script)
It does not help to run soffice from a small script like this
!# /bin/sh
SAL_ENABLE_FILE_LOCKING=0
/Applications/OpenOffice.org.app/Contents/MacOS/soffice

Does also not fix the issue but I am not sure that this is the correct
way to run it or if some other script overwrites the variable.

Any useful hints/advises?

Thanks
Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to