01-05-2011
@rdcwayx
@anchal khare
its not working
can u plz solve it..... its showing not found....
but the lines are in the file
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi all,
from a shell (ksh) script, i am doing a 'grep'. how do i find out the number of lines returned from that 'grep' command ??
thanks in advance. (4 Replies)
Discussion started by: cesarNZ
4 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I want to list filenames instead of lines when i search in compresed files for a string.
#gzcat *.gz | grep -l 12345
gives me:
<stdin>
Anyone got a solution on this problem? (2 Replies)
Discussion started by: HugoH
2 Replies
3. Shell Programming and Scripting
Hi All,
Please find my piece of code below. I am trying to grep the word SUCCESS from $LOGFILE and storing in the grepvar variable. And i am placing that variable in a file. Now if i open the file, i can see the four lines but not in seperate four line s but in a paragraph. If am mailing that log... (8 Replies)
Discussion started by: intiraju
8 Replies
4. Shell Programming and Scripting
Hi experts
I want the proper argument to the grep command so that I need to skip the first few lines(say first 10 lines) and print all the remaining instances of the grep output.
I tried to use grep -m 10 "search text" file*. But this gives the first 10 instances(lines) of the search string.... (7 Replies)
Discussion started by: ks_reddy
7 Replies
5. UNIX for Dummies Questions & Answers
I want to search files (basically .cc files) in /xx folder and subfolders.
Those files (*.cc files) must contain #include "header.h" AND x() function.
I am writing it another way to make it clear,
I wanna list of *.cc files that have 'header.h' & 'x()'. They must have two strings, header.h... (2 Replies)
Discussion started by: ritikaSharma
2 Replies
6. UNIX for Dummies Questions & Answers
The following grep command grep -v "^$" filename > newfilename does not populate the new file with any data. I see it search the entire input file but the output file never gets filled. Is this not the correct command for what Im looking to do? (2 Replies)
Discussion started by: aispg8
2 Replies
7. Solaris
For example a log file looks like below-
13:30:00-
abcdefghijklhjghjghjhskj.
abcdefghijkl.
14:15:00-
abcdefghijkl.
14:30:00-
abcdefghijkl.
14:35:00-
abcdefghijkl.
123456789.
123456789.
14:45:00-
abcdefghijkl. (0 Replies)
Discussion started by: dev_shivv
0 Replies
8. Shell Programming and Scripting
14:15:00-
abcdefghijkl.
14:30:00-
abcdefghijkl.
14:35:00-
abcdefghijkl.
123456789.
123456789.
14:45:00-
abcdefghijkl.
14:50:00-
abcdefghijkl.
123456789.
15:30:00-abcdefghijkl. (3 Replies)
Discussion started by: dev_shivv
3 Replies
9. AIX
HI All,
I am using grep command to serach a pattern in a list of files and storing the output in a variable. Then i am applying some logic on that variable to get the required output.
But Thing is that when the pattern is present mutiple times in a file, i am getting the output of grep in a... (3 Replies)
Discussion started by: goutam sahoo
3 Replies
10. AIX
I need to grep two lines from topas command in one of my AIX server.
Topas Monitor for host: semas001 EVENTS/QUEUES FILE/TTY
Wed Jan 29 10:12:06 2014 Interval: 2 Cswitch 764 Readch 4473.1K
Syscall 5166 ... (4 Replies)
Discussion started by: rpm120
4 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)