If I use the find command to find files older than n days I have to enter
find . -mtime +(n-1). I tried this on a Solaris 9 system and also Linux. Is this something that all Unix veterans know about (I'm new to Unix)? If so, maybe my man pages need to be updated (how to do this?). :confused: (4 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 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)
Hi guys, I am looking for a way of moving all files out of a directory with a time stamp greater then the one I specify. Can anyone suggest a way of doing so?
For example, move all files out of dir1 which were created after 17:00 into dir2.
Thanks :) (1 Reply)
Hi, so I was using mtime and its not behaving the way I would think its supposed too. I have two pdf files. One modified today and another 6 months ago. I upload them to the solaris server. Then I run the below find statements.
This finds my 2 files
find *.pdf -type f -name '*.pdf'
this finds... (2 Replies)
Hi Friends,
Please help me to sort out this problem, I am running this in centos o/s and whenever I run this script I am getting "find: missing argument to `-exec' " but when I run the same code in the command line I didn't find any problem. I am using perl script to run this ... (2 Replies)
Hi,
I'm trying to find all files that have a .ksh and .p extension and that are 7 days old by using the below find command but it doesn't seem to as expected. It gives me random results.. Can someone point out what may be wrong?
find . -name "*.ksh" -o -name "*.p" -mtime -7 (2 Replies)
I am trying to execute the cli.sh script in another shell script passing arguments and getting the below error.
Myscript.sh
#!/bin/sh
/home/runAJobCli/cli.sh runAJobCli -n $Taskname -t $Tasktype
I am passing the below 2 arguments and it giving error
./Myscript.sh T_SAMPLE_TEST MTT... (11 Replies)
Discussion started by: Info_Geek
11 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)