>From: Henk de Leeuw <[EMAIL PROTECTED]> >Sent: Mar 7, 2007 1:59 AM >To: James Mckenzie <[EMAIL PROTECTED]>, users@openoffice.org >Subject: Re: [users] Problem accessing files on NFS mounted volume > >James Mckenzie wrote: >>>> When I access files from within OpenOffice that are mounted on an >>>> NFS-mounted volume, I run into problems. >>>> Opening an existing file is terribly slow, and the resulting window >>>> has (read-only) at the top. >>>> Saving a file ends with a file that is 0 bytes in size, and an error >>>> message that the file could not be saved. >>>> When I open or save files from other programs (Firefox) or the command >>>> line on the NFS volume, I have no problems. >>>> Reading and writing local files from OpenOffice is also OK. >>>> Both NFS server and client run Linux. >>>> >> >From what I gather at >> >>> http://www.openoffice.org/issues/show_bug.cgi?id=36634 nfs is >>> unsupported by OOo :( >>> >> Wrong. It is and has been supported on the Mac. See issue 54586, which >> I just re-opened as it was also held by the same issue on the Mac OS X >> platform. I suggested looking at the code to see if it applies to >> other UNIXes and Linux. Disabling SAL_FILE_LOCKING is unsuitable in a >> multi-user environment and can lead to very interesting results. >> >Thanks for the pointer; Issue 54586 solved the problem for me (and not >with an insecure workaround!) >It appeared that on my workstation, the rpc.statd was not running. >This daemon handles file locking on NFS, which OpenOffice rightly uses, >and other programs apparently not. >That is why disabling file locking is a workaround.
Great. I still don't like the method of file locking used, but if it works for you, it works. However, the Mac fix should also work for UNIXy systems too. > >On my Gentoo workstation, I did rc-update add nfsmount default; rc; and >the problem was solved. >Other operating systems will have a similar way of handling this. Again, this was a good fix for you. However, if you read through the entire issue, there are folks that the above fixes do not work for, but the Mac fix might. It is best to use the 'best' method of file locked that should work even if the nfs system is broken, and it is on some Linux distros. > >So, this is not a bug in OOo, it is intended behaviour. >The error message could be a little less cryptic, that's all. Here is one point that you and I agree on. Less cryptic messages are always helpful. I like the one that I got at work after sitting for about 15 minutes "Unable to access the network resource" Huh? BTW, this was on the user friendly Windows operating system. Still, I would like to see the file locking used by the Mac port investigated by the Linux team to see if it will overcome some of the poorly designed and implemented NFS systems to make the user experience better. James McKenzie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
