On 11/06/2008 03:08 AM, 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 ?
OOo 3.0 made some significant changes to how file locking is implemented - see: http://www.openoffice.org/issues/show_bug.cgi?id=91015 [data loss using concurently OOo3 and another editor in the same network] http://www.openoffice.org/issues/show_bug.cgi?id=95528 [Let OOo use lock file mechanics for alien formats as well.] http://www.openoffice.org/issues/show_bug.cgi?id=95530 [Notify on closing/saving if the file was changed by other application.] There is considerable discussion regarding this on the release and development lists & 3.0.1 is supposed to address _some_ of the issues. You may want to read those bug/issue reports & participate in testing/commenting. In the interim, I'd recommend that you stay with 2.4.2 for the time being until the issue(s) is resolved. Also, note that StarOffice 9 (yet to be fully released) may have the same issues. However, generally Sun/SO tend to use OOo as a testing ground (hence the delay in releasing SO9), so perhaps they will have addressed the problem by the time they release. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
