I have seen several replies to this question. But none seem to address the original issue of the creation of the file itself. It has been my long understanding that file locking semantics are _NOT_ part of any data application program to start with. So any file for the purpose of file locking is totally unwarranted and undesirable.
It is the responsibility of the OS that is providing the file share service to adequately protect the file from operations that could cause any form of data loss or undesirable results. My two cents worth. James On Thursday 06 November 2008, Dieter Treichel wrote: > We are using staroffice 8 and openoffice 2 since 2006 on about 300 pc in > my school. The users are saving their data on their personal > samba-share. > Now we want to change to OO-3 and have the problem, that no user is able > to save data in his/her home-share. Cause is the new behaviour of open > office, to create a temporary file like .lockFilename. > > .Filename-files are vorbidden (veto file statement in the smb.conf ) for > this share. > > Is there any possibility to change the standard name for the temporary > files (they should not begin with a dot) ? > > Is it possibe to change the path for the temporary files without > changing the path to the working directory ? > > > Dieter > Powered by Open-Xchange.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
