How to see the first instance of an error in explorer log ?
In this case I want to know the first time error "SCSI transport failed" was populated in messages
Thanks
Amani
Probably a rookie answer here, but if you're talking just scanning for the first error in a given log file, I've used this logic successfully in the past:
so drop in "SCSI transport failed" for "<error>" and put your log file in there and it'll rip out 10 lines (5 before and 5 after) around the error.
Hello,
i'm running a hp-ux workstation model 715 / 100 with hp-ux version 11.11
i need a microsoft internet explorer for this workstation to make some tests. does anyone know where i can cat a internet explorer 4.01 for my workstation?
Thank all for help! ;-) (3 Replies)
Hello, i need some help about how to set up a high velocity impact printer in UNIX SCO 5.05,
this printer is attached with a parallel port in a PC(host), the host use tunemul to access unix.(this reference is just to ask you if this is a local or remote connection, just to be sure),
so, i... (2 Replies)
hiii
i want to know how to install explorer in sparc e-250 OS solaris 8 iam able to install the software
iam able to install the explorer,i use to run
#./explorer -q -e
other than this what all i should run to get all details.but iam just getting some thing which not related to o/s or h/w... (3 Replies)
All,
I looking for developing a script which would find the first instance of a date in a log file:
2004/07/15 19:16:09
Here are the next couple lines after the dat time stamp:
backup completed
daemon started.
And I want to put the rest of the lines after the first instance in this... (2 Replies)
Hi there, I have upgraded my explorer (SUNWexplo) on a solaris 10 Sparc box from version 3.4 to the latest version (5.5) . However im a little concerned, whenever I run the new explorer either manually or scheduled, I get a syslog event as follows
1 in 0:08:31: Sep 22 17:00:15 fmy.machine.com... (8 Replies)
Alright, I think I know what I am doing with sed(which probably means I don't). But I cant figure out how to replace just the first occurance of a string. I have tried sed, ed, and grep but can't seem to figure it out. If you have any suggestions I am open to anything! (3 Replies)
I wrote a script to capture some rows from the DB.
However I want to capture the errors if the DB instance is down which usually produces errors like below. What should be my approach to kill script if the DB instance is down:
DATABASE ERRORS:
Msg 937, Level 14, State 1:
Server... (2 Replies)
I issue the following command to create a boot instance from an active boot instance on solaris 11.1.
beadm create -a -d "Oracle x86 64 BIT Solaris SunOS Rel 5.11 Ver 11.1 10/2012 Enable SSH " OraSolBcp
I get the following error below;-
be_mount_callback: failed to mount dataset... (5 Replies)
Team ,
I am trying to sudo to instnace using a shell script .In out put i am getting this error for every line ...I am running this script as root ..
sudo su - userid -i db2 "command "
Error
/etc/profile: shopt: not found
how can we overcome this error ? Can someone help on... (1 Reply)
Discussion started by: rocking77
1 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)