02-20-2013
The -s 300 -c 288 should work okay. I still recommend changing to 6 minute intervals and 240 entries. Works much better with nmon_analyzer and consolidated/trend views (excel and/or analyzer does not like more than ±250 entries and averages them to get number of entries below 250 - so 288 becomes 144 "values".
When using the "bare analyzer" you can have more.
OK. What version of AIX (with nmon included) - or are you still using a downloaded version - and are they different between the archived versions (that you had compressed) and the ones that are working - or are none working?
It will be 24 hours, but I'll try deleting the BBBP lines and see what happens with my reports.
This User Gave Thanks to MichaelFelt For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am facing the following issue when using db2. The JDBC prepared statement command is sending an incorrect value to the database for search. I did a truss on the app and here is the log. I want to know what is the value that is getting passed. is it possible.
26867/68: send(62,... (2 Replies)
Discussion started by: buytamil
2 Replies
2. AIX
Anyone ever experienced a core dump when running NMON. I am running AIX 5.3 on an 8 CPU LPAR (P570). This has only recently started to happen. (3 Replies)
Discussion started by: johnf
3 Replies
3. AIX
Can any one help where i can find articals about nomn
I need to know how to read this tools
┌─CPU-Utilisation-Small-View───────────────────────────────────────────────────â”
│ 0----------25-----------50----------75----------100│
│CPU User% Sys% Wait% Idle%| ... (3 Replies)
Discussion started by: habuzahra
3 Replies
4. UNIX for Dummies Questions & Answers
Is it possible to track the progress of a job (informatica) by analysing the progress of it's log file ? I have a long running job, and no way of tracking how far allong it is. Thanks. (4 Replies)
Discussion started by: cosmos328is
4 Replies
5. HP-UX
Hi,
Is there any way to find the mode of the binary file (debug or release) by analyzing the core file generated by that binary on the HPUX11i Platform? (5 Replies)
Discussion started by: Prajakta
5 Replies
6. UNIX for Dummies Questions & Answers
I'm not sure if this query is relevant to this forum but here goes anyways...
I want analyse log files that do not appear to be of standard format. I have tried using Analog but cannot config it to read the files.
Does anyone have any advice on working with log files taken from a Unix... (6 Replies)
Discussion started by: Sepia
6 Replies
7. Solaris
Friends
I was trying to analyse a core dump using pstack command in Sol5.9(Sparc)
The output is as below.
root: pstack core_mumux211_istauth_220_108_1229517198_21922
core 'core_mumux211_istauth_220_108_1229517198_21922' of 21922: istauth
fe1afbb8 ttcdrv (c10e0, c1db4, 30ad8, bc950, 0, 0)... (1 Reply)
Discussion started by: efunds
1 Replies
8. Shell Programming and Scripting
Hello,
I have a list of e-mails. I need to know, which email-s from that list not use. I want to do this things:
- take email address from email list
- find this address in mail logs
- if, there is no record about this e-mail adress in list, show this e-mail address on screen
I did... (0 Replies)
Discussion started by: naezdnik
0 Replies
9. Shell Programming and Scripting
Hi,
I have below type of data in a text file in unix.
Emp_Name Emp_Dept
Raj 101
Amruta 100
Shilpa 100
Rohit 123
Amol 198
Rosh 101
Gaurav 198
Number of employees can be even more.
Need a command or a... (2 Replies)
Discussion started by: rajneesh_kapoor
2 Replies
10. Shell Programming and Scripting
Attached is the log file that I have generated through the following script:
last | head -2 |sed '2q;d' |awk '{ print $1"\t"$2"\t"$3"\t\t"$4"\t"$5"\t"$6"\t"$7"\t"$8"\t" $9"\t"$10"\t"$11}'>>/var/log/logadmin/logtest.txt
But now I'm unable to run the following operations on it:
1. Count... (1 Reply)
Discussion started by: Lionking93
1 Replies
LEARN ABOUT DEBIAN
kinosearch1::queryparser::queryparser
KinoSearch1::QueryParser::QueryParser(3pm) User Contributed Perl Documentation KinoSearch1::QueryParser::QueryParser(3pm)
NAME
KinoSearch1::QueryParser::QueryParser - transform a string into a Query object
SYNOPSIS
my $query_parser = KinoSearch1::QueryParser::QueryParser->new(
analyzer => $analyzer,
fields => [ 'bodytext' ],
);
my $query = $query_parser->parse( $query_string );
my $hits = $searcher->search( query => $query );
DESCRIPTION
The QueryParser accepts search strings as input and produces Query objects, suitable for feeding into KinoSearch1::Searcher.
Syntax
The following constructs are recognized by QueryParser.
o Boolean operators 'AND', 'OR', and 'AND NOT'.
o Prepented +plus and -minus, indicating that the labeled entity should be either required or forbidden -- be it a single word, a phrase,
or a parenthetical group.
o Logical groups, delimited by parentheses.
o Phrases, delimited by double quotes.
o Field-specific terms, in the form of "fieldname:termtext". (The field specified by fieldname will be used instead of the QueryParser's
default fields).
A field can also be given to a logical group, in which case it is the same as if the field had been prepended onto every term in the
group. For example: "foo:(bar baz)" is the same as "foo:bar foo:baz".
METHODS
new
my $query_parser = KinoSearch1::QueryParser::QueryParser->new(
analyzer => $analyzer, # required
fields => [ 'bodytext' ], # required
default_boolop => 'AND', # default: 'OR'
);
Constructor. Takes hash-style parameters:
o analyzer - An object which subclasses KinoSearch1::Analysis::Analyzer. This must be identical to the Analyzer used at index-time, or
the results won't match up.
o fields - the names of the fields which will be searched against. Must be supplied as an arrayref.
o default_field - deprecated. Use "fields" instead.
o default_boolop - two possible values: 'AND' and 'OR'. The default is 'OR', which means: return documents which match any of the query
terms. If you want only documents which match all of the query terms, set this to 'AND'.
parse
my $query = $query_parser->parse( $query_string );
Turn a query string into a Query object. Depending on the contents of the query string, the returned object could be any one of several
subclasses of KinoSearch1::Search::Query.
COPYRIGHT
Copyright 2005-2010 Marvin Humphrey
LICENSE, DISCLAIMER, BUGS, etc.
See KinoSearch1 version 1.00.
perl v5.14.2 2011-11-15 KinoSearch1::QueryParser::QueryParser(3pm)