On Sat, 15 Sep 2012, Mirosław Zalewski wrote:
On 15/09/2012 at 19:38, Felmon Davis <firstname.lastname@example.org> wrote:
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?
Yes, they does.
On filesystem-level, directory is (roughly speaking) special file with names of
other files. If you create file, then this list gets updated (directory
modification time changes). If you remove that file, then it gets updated again.
I don't know about OP backup tools (did not read whole thread), but rsync has
--ignore-times and --size-only command-line options which may come handy in
wouldn't really help her. I was pointing out that it is not enough to
worry about the file's time-stamp; the directory's time-stamp is also
altered. if her backup software is sensitive to the latter, then she's
no further along. if the backup software isn't sensitive to directory
time-stamps, then fine, my point is moot.
still, I'm surprised if there is no way to tell LO not to make a lock
file. googling suggests there might be, see 'libreoffice disable file
locking' or similar.
Happiness is having a scratch for every itch. -- Ogden Nash
For unsubscribe instructions e-mail to: email@example.com
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
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy