03-13-2017
Um, okay. Please help us.
I assume the output differs on the very same directory tree. Could please post what you found as the difference?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to figure out the syntax to use find to remove files older than 30 minutes. I know that this will work for files 1 day old, but cannot seem to trim the time down to 30 minutes.
find /path/to/file -ctime +1 -exec rm -f {} \; (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. Shell Programming and Scripting
Can any one tell me how to find out ctime , mtime ,atime for a file/directory on unix.
Cheers,
Nilesh (5 Replies)
Discussion started by: nilesrex
5 Replies
3. UNIX for Dummies Questions & Answers
Hi, I am using Solaris 5.8
I searched online, the find command has an option called maxdepth which can be used to limit the number of directories find will look into.
find . -maxdepth 2 -type f
When I run the above command in solaris, I get an error
find: bad option -maxdepth
find:... (2 Replies)
Discussion started by: Leion
2 Replies
4. UNIX for Dummies Questions & Answers
Hi
I wish to find only files in dir /srv/container/content/imz06/. It means exclude subfolder /srv/container/content/imz06/archive/
> uname -a
SunOS testbox6 5.10 Generic_139555-08 sun4v sparc SUNW,Sun-Blade-T6320Its Solaris default "find"
> find /srv/container/content/imz06/* -name... (4 Replies)
Discussion started by: slashdotweenie
4 Replies
5. Shell Programming and Scripting
I know that find -ctime +1 will find ALL files that have been modified
that are greater than 1 day old and -ctime 1 will find files that are
ONLY 1 day old -ctime -1 mean files that are less than a day old?
Can find actually use this granularity? (5 Replies)
Discussion started by: BeefStu
5 Replies
6. Shell Programming and Scripting
startdate="2012_07_04-16:14:4"
path1="/home/drdos/sample"
days=0
find $path1 -name "*$startdate*" > teste.txt
while
do
find $path1 -name "*.zip" ctime $days > teste.txt
days=`expr $days + 1`
done
echo " Files that are near the string u search are on teste.txt"Hi to... (2 Replies)
Discussion started by: drd0spt
2 Replies
7. Shell Programming and Scripting
Can you please figure out what is the issue here
$ find . -maxdepth 1 -type f -size 0 -print
find: bad option -maxdepth
please find the OS details
$ uname -a
HP-UX g5u1216 B.11.31 U ia64 2614088426 unlimited-user license
Use code tags, thanks. (6 Replies)
Discussion started by: TomG
6 Replies
8. Answers to Frequently Asked Questions
When I use the command find "/abc/xyz" -type f -ctime +30 getting the error as
find:"/abc/xyz /lost+found: Permission Denied"
I tired find "/abc/xyz" -type d \( ! lost+found \) -type f -ctime +30 The error is
find: paths must precede expression Usage: find
Tried find "/abc/xyz"... (1 Reply)
Discussion started by: anithab
1 Replies
9. Shell Programming and Scripting
The problem is this one. I tar and gzip files on remote server
Code:
find . -ctime -1 | tar -cvf transfer_dmz_start_daily.tar *${Today}*.*;
Command
Code:
find . -ctime -1
Doesn't find files without extension
Code:
.csv .txt
I have to collect all files for current... (1 Reply)
Discussion started by: digioleg54
1 Replies
10. Shell Programming and Scripting
The problem is this one. I tar and gzip files on remote server
find . -ctime -1 | tar -cvf transfer_dmz_start_daily.tar *${Today}*.*;
Command
find . -ctime -1
Doesn't find files without extension
.csv .txt
I have to collect all files for current day, when the program... (1 Reply)
Discussion started by: digioleg54
1 Replies
LEARN ABOUT MOJAVE
git-ls-tree
GIT-LS-TREE(1) Git Manual GIT-LS-TREE(1)
NAME
git-ls-tree - List the contents of a tree object
SYNOPSIS
git ls-tree [-d] [-r] [-t] [-l] [-z]
[--name-only] [--name-status] [--full-name] [--full-tree] [--abbrev[=<n>]]
<tree-ish> [<path>...]
DESCRIPTION
Lists the contents of a given tree object, like what "/bin/ls -a" does in the current working directory. Note that:
o the behaviour is slightly different from that of "/bin/ls" in that the <path> denotes just a list of patterns to match, e.g. so
specifying directory name (without -r) will behave differently, and order of the arguments does not matter.
o the behaviour is similar to that of "/bin/ls" in that the <path> is taken as relative to the current working directory. E.g. when you
are in a directory sub that has a directory dir, you can run git ls-tree -r HEAD dir to list the contents of the tree (that is sub/dir
in HEAD). You don't want to give a tree that is not at the root level (e.g. git ls-tree -r HEAD:sub dir) in this case, as that would
result in asking for sub/sub/dir in the HEAD commit. However, the current working directory can be ignored by passing --full-tree
option.
OPTIONS
<tree-ish>
Id of a tree-ish.
-d
Show only the named tree entry itself, not its children.
-r
Recurse into sub-trees.
-t
Show tree entries even when going to recurse them. Has no effect if -r was not passed. -d implies -t.
-l, --long
Show object size of blob (file) entries.
-z
line termination on output and do not quote filenames. See OUTPUT FORMAT below for more information.
--name-only, --name-status
List only filenames (instead of the "long" output), one per line.
--abbrev[=<n>]
Instead of showing the full 40-byte hexadecimal object lines, show only a partial prefix. Non default number of digits can be specified
with --abbrev=<n>.
--full-name
Instead of showing the path names relative to the current working directory, show the full path names.
--full-tree
Do not limit the listing to the current working directory. Implies --full-name.
[<path>...]
When paths are given, show them (note that this isn't really raw pathnames, but rather a list of patterns to match). Otherwise
implicitly uses the root level of the tree as the sole path argument.
OUTPUT FORMAT
<mode> SP <type> SP <object> TAB <file>
This output format is compatible with what --index-info --stdin of git update-index expects.
When the -l option is used, format changes to
<mode> SP <type> SP <object> SP <object size> TAB <file>
Object size identified by <object> is given in bytes, and right-justified with minimum width of 7 characters. Object size is given only for
blobs (file) entries; for other entries - character is used in place of size.
Without the -z option, pathnames with "unusual" characters are quoted as explained for the configuration variable core.quotePath (see git-
config(1)). Using -z the filename is output verbatim and the line is terminated by a NUL byte.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-LS-TREE(1)