ls -ltr | grep string
How can I use regular expressions to filter the results provided even more. I am using the above command as a reference. (1 Reply)
Hi,
Wondering if anyone could help me with a simple script to filter out multiple things from a file.
Right now I just have long lines of grep -v remove file | greg -v etc etc
What I would like to do is have grep -v <run everything in a file> tofilter
If that makes sense. Basically a... (2 Replies)
Hi Folk,
Following is the command I used to get data related to the DataFlowEngine.
I wanted to know the % usage of cpu and memory.
ps avg | grep Data
This command will show the processes with its PID as :
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
... (1 Reply)
Hello,
I'm working on unix with grep (GNU grep) 2.5.1. I'm going through some of the newer regex syntax using Regular Expression Reference - Advanced Syntax a guide.
ls -aLl /bin | grep "\(x\)"
Which works, just highlights 'x' where ever, when ever.
I'm trying to to get (?:) to work but... (4 Replies)
I have ran into a small issue and I am not sure how to fix it.
In one of our current scripts we have this line which does a grep to get the pid of the process.
ps -ef | grep nco_p_syslog | grep $x | awk '{print $2}'
However this is not returning anything due to the how long the value... (7 Replies)
I am attempting to figure out how to only capture part of a grep command I am doing. So far no luck.
When I execute....
leviathan:/gfs/home/tivoli>ps -ef | /usr/ucb/ps -auxww | grep nco_p_syslog
The results are....
tivoli 10185 0.0 0.0 5888 5168 ? S Oct 23 0:26... (2 Replies)
I am running a grep query for searching a pattern, and the output is quite huge. I want only the last 200 lines to be displayed, and I am not sure if tail will do the trick (can tail read from std in/out instead of files?).
Please help me out. (1 Reply)
Hi,
I can write sh script for Linux platform
I run:
netstat -an | grep -P '\:'38''| grep ESTABLISHED
but result:
# netstat -an | grep -P '\:'38''| grep ESTABLISHED
tcp 0 0 172.16.1.107:383 172.16.1.81:49981 ESTABLISHED
tcp 0 0... (8 Replies)
I have a large file of many pairs of sequences and their headers, which always begin with '>'
I'm looking for help on how to retain only sequences (and their headers) below a certain length. So if min length was 10, output would be
I can filter by length, but I'm not sure how to exclude... (3 Replies)
Hi,
I am having a file like below
hello how are you
hello... (5 Replies)
Discussion started by: rohit_shinez
5 Replies
LEARN ABOUT OSX
svk::command::log
SVK::Command::Log(3) User Contributed Perl Documentation SVK::Command::Log(3)NAME
SVK::Command::Log - Show log messages for revisions
SYNOPSIS
log DEPOTPATH
log PATH
log -r N[:M] [DEPOT]PATH
OPTIONS -r [--revision] ARG : ARG (some commands also take ARG1:ARG2 range)
A revision argument can be one of:
"HEAD" latest in repository
{DATE} revision at start of the date
NUMBER revision number
NUMBER@ interpret as remote revision number
NUM1:NUM2 revision range
Unlike other commands, negative NUMBER has no
meaning.
-l [--limit] REV : stop after displaying REV revisions
-q [--quiet] : Don't display the actual log message itself
-x [--cross] : track revisions copied from elsewhere
-v [--verbose] : print extra information
--xml : display the log messages in XML format
--filter FILTER : select revisions based on FILTER
--output FILTER : display logs using the given FILTER
DESCRIPTION
Display the log messages and other meta-data associated with revisions.
SVK provides a flexible system allowing log messages and other revision properties to be displayed and processed in many ways. This
flexibility comes through the use of "log filters." Log filters are of two types: selection and output. Selection filters determine which
revisions are included in the output, while output filters determine how the information about those revisions is displayed. Here's a
simple example. These two invocations produce equivalent output:
svk log -l 5 //local/project
svk log --filter "head 5" --output std //local/project
The "head" filter chooses only the first revisions that it encounters, in this case, the first 5 revisions. The "std" filter displays the
revisions using SVK's default output format.
Selection filters can be connected together into pipelines. For example, to see the first 3 revisions with log messages containing the
string 'needle', we might do this
svk log --filter "grep needle | head 3" //local/project
That example introduced the "grep" filter. The argument for the grep filter is a valid Perl pattern (with any '|' characters as '|' and
'' as '\'). A revision is allowed to continue to the next stage of the pipeline if the revision's log message matches the pattern. If
we wanted to search only the first 10 revisions for 'needle' we could use either of the following commands
svk log --filter "head 10 | grep needle" //local/project
svk log -l 10 --filter "grep needle" //local/project
You may change SVK's default output filter by setting the SVKLOGOUTPUT environment. See svk help environment for details.
Standard Filters
The following log filters are included with the standard SVK distribution:
Selection : grep, head, author
Output : std, xml
For detailed documentation about any of these filters, try "perldoc SVK::Log::Filter::Name" where "Name" is "Grep", "Head", "XML", etc..
Other log filters are available from CPAN <http://search.cpan.org> by searching for "SVK::Log::Filter". For details on writing log
filters, see the documentation for the SVK::Log::Filter module.
perl v5.10.0 2008-08-04 SVK::Command::Log(3)