Re: [libreoffice-users] Re: not create a dot file in same folder as document when opening it for viewing

On Sat, 15 Sep 2012, Jay Lozier wrote:

> On 09/15/2012 02:28 AM, Jean-Francois Nifenecker wrote:
> > Le 13/09/2012 16:39, Jay Lozier a écrit :
> > > Why do you want to stop the creation of lock files?
> >
> > As I understand Enda's request, the problem lies in the following
> > situation:
> >
> > 1. she opens an ODF file using LibO.
> > 2. LibO automatically creates the .~lock flag thingy.
> > 3. she closes the ODF file without any edition, hence the ODF file
> > contents is not changed [1]
> > 4. the .~lock flag file is deleted
> >
> > But now, the directory is flagged as having changed because of the
> > .~lock file creation/deletion. Then her backup tool stalls on this
> > directory that should in fact be ignored.
> >
> > IMO, this is a problem with the backup tool, not LibO. But Enda didn't
> > give many details about that part of the process.
> >
> > [1] important note: at this point, the operating system records the
> > last access time, which could also lead your backup system to process
> > that file. There could be some option in the tool that might disable
> > that functionnality.
> Jean,
>
> Following up on your comment I did the following:
>
> 1. Opened an ODF file in LO
> 2. Verified the creation of the lock
> 3. Made changes to file
> 4. Undid all changes
> 5.Closed file, which deleted the lock file
>
> I noticed when closing the file I was asked to save or discard the
> changes. I choose discard and the file time stamp was unchanged.
>
> I repeated the above and Saved the changes and the time stamp changed.
>
> The creation of the lock file has no affect on the ODF file time stamp.
> Checking the properties of ODF files shows both last changed and last
> accessed. I would think if the last changed date was later than the last
> time a backup was run the file is backed otherwise the file is not
> backed up. The last accessed date does not always match the last changed
> date.

question: doesn't the Linux file system (ext2; ext3) register access 
time to a directory? in that case, wouldn't writing a file to a 
directory register in the directory's time-stamp? if the OP's back-up 
methodology is sensitive to that, the problem would remain.

am I off the track?

F.

--
Felmon Davis

The more things change, the more they stay insane.  -- Tom Weller
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted