Brian Barker wrote:
> At 12:08 06/11/2008 +0100, 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 forbidden (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 possible to change the path for the temporary files without
> > changing the path to the working directory ?
> >
> I don't know the answer to this, but I can mention another
> disadvantage
> with the new arrangement.
>
> If I open an OpenOffice document to read it or perhaps to copy
> material
> from it and then close the document without making changes or saving
> it,
> the modification date and time on the file are not changed. This is
> correct. But the modification date and time on the containing folder
> *are* changed, because two changes have been made to it - the creation
> and then deletion of the lock file. The folder and its contents,
> though, are just as they were. This is perhaps unhelpful, and could be
> avoided if the lock files were saved somewhere else - perhaps in a
> common location, as suggested above.
>
>I beg to differ: I don't think that's at all unreasonable behaviour.
>Even if you open a file in OOo just to read it, it is nevertheless
>opened in r/w mode, and it therefore needs to be locked because the
>system can't read the user's mind -- it might be helpful if there were
>an open-read-only facility if this is an issue. So the date changes are
>correct.
>
>Lock files have to exist alongside the original if they're to be any
>use
>in a networked environment - different machines may have different
>ideas
>of the suggested "common location".
>
>I think the OP needs to get his samba config changed - that seems to me
>to be the real issue. I wasn't actually aware 'dot' files could be
>prohibited under samba - and my own OOo v3 running under XP works very
>happily using a samba share.
>
>BTW 'dot' files do seem to be a general windows issue: try using
>R-click
<and New|Text File under explorer to create a file called .xyzzy - it
>won't do it ("file name needed" or some such).
I will try to explain my problem with the dot-Files:
The server is set up to supply windows- and linux-clients. The
linux-clients needs a lot of dot-files in the homes of the user.
These files should not be visible using the windows-clients. For this
purpose there is the Veto-file-statement in the smb.conf-file. It
has never been a problem before.
I would be glad to get a change in the behaviour of OOo-3.
thanks
Dieter
Powered by Open-Xchange.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
