Hi Stephan,
From the "general i/o error" in your screenshot, and just a wild
guess: Could it have anything to do with NFS and file locking (see
issue 54586)? If your remote access is via NFS, and if OOo on Mac
uses file locking as it does on Linux and Solaris (I have no idea),
you could try the following: In the soffice script (in OOo's
program directory), comment out the lines
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING
by prefixing them with '#'. (If there are no such lines, it
probably means that OOo on Mac does not use file locking...)
Maybe it will work, maybe not. Some french users reported similar
issues (recently, at least three users reported to have problems with
OOo2.0 on network, on Mac OS X, using or not Mac OS X server), and at
least for two, it was *not* the solution. I wonder if there is not a
bigger issues behind network use of OpenOffice.org2.0 on Mac OS X.
No idea about the real problem, but if this can help, they're
several possibilities, and we first must inventory what works and
what not.
Possibilities are given by the OS version server/client, and the used
file system. 3 currently mounted file system are possible : SMB
(samba), AFS ( Apple system), NFS.
As a workaround, Patrick Luby proposed a fix for this type of problem
in it"s code donation, and I'll build a special version to try. I
just need two or three days ( I have to build an m143 for Linux PPC
with the same machine before).
For Guy Bechet : contact me directly, and we will try to find a
solution : I'll build a special version including Patrick Luby's fix,
to see.
Please, be comprehensive : we have not a big experience of newtorking
with OOo2.0 plus we only use local machines to build and fix bugs.
Regards,
eric bachard
Le 7 déc. 05 à 08:57, Stephan Bergmann a écrit :
GB wrote:
Hi,
This may be a bug with Open Office 2.0 ?
$ uname -a
Darwin R-PUNIX-MAC-OSX-BECHE018.local 8.3.0 Darwin Kernel Version
8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/
RELEASE_PPC Power Macintosh powerpc
On the file here, you can see that I didn't succeeded in working
on remote disks. The error message says there is an input/output
error.
It's impossible to open or to save a file on a remote disk.
Nevertheless the file is created on the remote disk, with the good
name, but it is empty. On the error message Ooo speaks about a
file "sans nom1", althought I gave it, a name.
On my local disk all is OK.
I work in a large company, 100% Windows and Office Microsoft ; So
I tried to face the dictatorship with my Macintosh, but we work
primarily on data distributed on remote disks : I cannot thus,
use Ooo because of this error.
Ooo is great. Congratulations for this very great work.
Guy Béchet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
