How to grep only IP 10.76.178.xx? Post: 302880732

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

MEM=`ps v $PPID| grep -i db2 | grep -v grep| awk '{ if ( $7 ~ " " ) { print 0 } else

Hi Guys, I need to set the value of $7 to zero in case $7 is NULL. I've tried the below command but doesn't work. Any ideas. thanks guys. MEM=`ps v $PPID| grep -i db2 | grep -v grep| awk '{ if ( $7 ~ " " ) { print 0 } else { print $7}}' ` Harby.

2. UNIX for Dummies Questions & Answers

| help | unix | grep (GNU grep) 2.5.1 | advanced regex syntax

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...

3. Shell Programming and Scripting

AWK/GREP: grep only lines starting with integer

I have an input file 12.4 1.72849432773174e+01 -7.74784188610632e+01 12.5 9.59432114416327e-01 -7.87018212757537e+01 15.6 5.20139995965960e-01 -5.61612429666624e+01 29.3 3.76696387248366e+00 -7.42896194101892e+01 32.1 1.86899877018077e+01 -7.56508762501408e+01 35 6.98857157014640e+00...

4. UNIX for Dummies Questions & Answers

Bash - CLI - grep - Passing result to grep through pipe

Hello. I want to get all modules which are loaded and which name are exactly 2 characters long and not more than 2 characters and begin with "nv" lsmod | (e)grep '^nv???????????? I want to get all modules which are loaded and which name begin with "nv" and are 2 to 7 characters long ...

5. UNIX for Advanced & Expert Users

HPUX_SCHED_NOAGE 178

We are getting the error below in Linux - Oracle 11g Bench as below: Last System configure: NOTE: Fri May 18 17:34:32 IST 2012: creating SPFILE ... CREATE SPFILE='<path>/ORACLE/admin/eml100_1/pfile/spfile.ora.UPD' FROM PFILE='<path>/ORACLE/admin/eml100_1/pfile/config.ora' * ERROR at line...

6. Shell Programming and Scripting

Inconsistent `ps -eaf -o args | grep -i sfs_pcard_load_file.ksh | grep -v grep | wc -l`

i have this line of code that looks for the same file if it is currently running and returns the count. `ps -eaf -o args | grep -i sfs_pcard_load_file.ksh | grep -v grep | wc -l` basically it is assigned to a variable ISRUNNING=`ps -eaf -o args | grep -i sfs_pcard_load_file.ksh |...

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)