:D i have a slight problem and would appreciate if someone could clarify the confusion.. i use find alot and so far i have done ok.. but it just struck me a couple of days ago that I am not quite sure what the difference between the modification time and the change time as in ctime and mtime and... (3 Replies)
...what am i doing wrong??
I need to find all files older than 30 days and delete but I can't get it to pull details for ANY + times. The file below has a time stamp which is older than 1 day, however if I try and select it using any of the -time flags it just doesn't see it. (the same thing... (1 Reply)
Hi,
I've some files of some past days and everyday some new files are also getting added to the same.
Now how can i use mtime to get the files of the current date i.e if i want the files of 25th feb 2009 and if im finding the files on 25th 12:10 am then i should only get the files after... (4 Replies)
Hi
I've made some test with perl script to learn more about mtime...
So, my question is :
Why the mtime from findfind /usr/local/sbin -ctime -1 -mtime -1 \( -name "*.log" -o -name "*.gz" \) -print are not the same as mtime from unix/linux in ls -ltr or in stat() function in perl : stat -... (2 Replies)
Dear all,
i am trying to find all files created one day before, for example 26 October, and i am using this command:
find . -type f -daystart -mtime 1
This command in fact lists all files created on 26 October, but the files between midnight 00:00 26 Oct and 01:00 26 Oct, does not shown... (4 Replies)
Discussion started by: arrals_vl
4 Replies
LEARN ABOUT DEBIAN
metastore
metastore(1) General Commands Manual metastore(1)NAME
metastore - stores and restores filesystem metadata
SYNOPSIS
metastore ACTION [OPTION...] [PATH...]
DESCRIPTION
Stores or restores metadata (owner, group, permissions, xattrs and optionally mtime) for a filesystem tree. This can be used to preserve
the metadata in situations where it is usually not stored (git and tar for example) or as a tripwire like mechanism to detect any changes
to metadata. Note that e.g. SELinux stores its labels in xattrs so care should be taken when applying stored metadata to make sure that
system security is not compromised.
ACTIONS -c, --compare
Shows the difference between the stored and real metadata.
-s, --save
Saves the current metadata to ./.metadata or to the specified file (see --file option below).
-a, --apply
Attempts to apply the stored metadata to the file system.
-h, --help
Prints a help message and exits.
OPTIONS -v, --verbose
Causes metastore to print more verbose messages. Can be repeated more than once for even more verbosity.
-q, --quiet
Causes metastore to print less verbose messages. Can be repeated more than once for even less verbosity.
-m, --mtime
Causes metastore to also take mtime into account for the compare or apply actions.
-e, --empty-dirs
Also attempts to recreate missing empty directories. May be useful where empty directories are not tracked (e.g. by git or cvs).
Only works in combination with the apply option. This is currently an experimental feature.
-f <file>, --file <file>
Causes the metadata to be saved, read from the specified file rather than ./.metadata.
PATHS
If no path is specified, metastore will use the current directory as the basis for the actions. This is the recommended way of executing
metastore. Alternatively, one or more paths can be specified and they will each be examined. Later invocations should be made using the
exact same paths to ensure that the stored metadata is interpreted correctly.
AUTHOR
Written by David Hardeman <david@hardeman.nu>
May 2007 metastore(1)