01-19-2017
Quote:
Originally Posted by
mohtashims
@Andrew: I tried your suggestion for nawk instead of awk but it failed.
By now you should know the routine:
what failed?
Which way did it fail? Show us your script, show us the error message it produced, show us the return codes, log entries, diagnostic messages or whatever sheds light on the problem.
Finally: did you try what i told you? And - if it didn't work either - how did it not work (same as/see above)?
I don't want to threaten you but i am probably one of a (rapidly dwindling) group willing to even read, let alone answer, your threads. You show so little effort in even trying to understand what one tells you that it is frustrating. This way you have turned away most of the knowledgeable people writing here. They simply do not deem it worth their time trying to help a hopeless cause.
If you do not want to further reduce this group to zero and to avoid your threads being met by stony silence only you need to understand that your problem, regardless of us helping you or not, still remains
your problem. You have to put
effort (read: work and thinking) into finding a solution and that means at the very least to describe the problem as detailed as possible and to provide necessary information proactively instead of only after being asked. We are willing to recognize the intent and overlook deficiencies in the work but you don't even show the intent and this is what drives many of my friends here away. We may help you to help yourself but we are not your paid helpdesk. Furthermore we have no responsibilty to help you, we do it for fun - but in helping you there is no fun at all.
You may want to think about that.
bakunin
These 2 Users Gave Thanks to bakunin For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Can anyone explain to me why the first line doesn't work and the second seems to work fine. I am trying to find all occurances of text within a certain column (col 13) that start with the character V, I suppose it sounds simple but I have tried using the following but don't really understand what... (2 Replies)
Discussion started by: Gerry405
2 Replies
2. Shell Programming and Scripting
hi,
i have the command nawk -v i want to use it equivalent in awk?
any help please
:) (2 Replies)
Discussion started by: kamel.seg
2 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I can run the following script using nawk..However, I find that teh server dun support nawk.. May I know how to change teh script to use awk such that it will work? Very urgent.. thx!
nawk 'BEGIN {FS=OFS=","}
NR==FNR{arr=$2;next}
$0 !~ "Documentation"{print $0;next} ... (2 Replies)
Discussion started by: kinmak
2 Replies
4. Shell Programming and Scripting
i'm new to shell scripting and have a problem please help me
in the script i have a nawk block which has a variable count
nawk{
.
.
.
count=count+1
print count
}
now i want to access the value of the count variable outside the awk block,like..
s=`expr count / m`
(m is... (5 Replies)
Discussion started by: saniya
5 Replies
5. Shell Programming and Scripting
Hi guys I'm very new to unix and I have to create an awk script that detects webpage addresses from a file/webpage and outputs how many times each webpage was detected.e.g. if my file was:
(Note: The symbol " was added to stop them being created into links)
"www.google.com"... (1 Reply)
Discussion started by: ROFL
1 Replies
6. Shell Programming and Scripting
Hi guys I'm very new to unix and I have to create an awk script that detects webpage addresses from a file/webpage and outputs how many times each webpage was detected.e.g. if my file was:
www.google.com
www.facebook.com
www.google.com
the output should be:
www.google.com x2... (2 Replies)
Discussion started by: ROFL
2 Replies
7. UNIX for Dummies Questions & Answers
Hi everyone,
i am new to unix , so i want to know what is the use of awk and nawk.
because in most of the place this cmds were used.
so, if anyone provied the basic idea of this cmds, it will be much helpfull for me . . ..
Thnks in Advance :) (9 Replies)
Discussion started by: natraj005
9 Replies
8. Shell Programming and Scripting
Hi Guys,
I am in need of some help; I have an xml message file which contains personal details as shown below:
, message=, message=, message=, message=, message=, message=
I want to use nawk to parse these xml messages but I am new to awk and nawk.
What I want is to get output... (7 Replies)
Discussion started by: James_Owen
7 Replies
9. Shell Programming and Scripting
Hi ! programmers
I have a need of detecting empty field in file
my file looks like this
40.900|-71.600|1.6|20|1|1961|21.00|3.700||1|US|28035|10029370|31
40.900|-71.600|5.7|20|1|1961|21.00|3.700||1|US|28035|10029370|31
40.900|-71.600|7.8|20|1|1961|21.00|3.700||1|US|28035|10029370|31... (7 Replies)
Discussion started by: Dona Clara
7 Replies
LEARN ABOUT OSX
apache::testsmoke
Apache::TestSmoke(3) User Contributed Perl Documentation Apache::TestSmoke(3)
NAME
Apache::TestSmoke - Special Tests Sequence Failure Finder
SYNOPSIS
# get the usage and the default values
% t/SMOKE -help
# repeat all tests 5 times and save the report into
# the file 'myreport'
% t/SMOKE -times=5 -report=myreport
# run all tests default number of iterations, and repeat tests
# default number of times
% t/SMOKE
# same as above but work only the specified tests
% t/SMOKE foo/bar foo/tar
# run once a sequence of tests in a non-random mode
# e.g. when trying to reduce a known long sequence that fails
% t/SMOKE -order=rotate -times=1 foo/bar foo/tar
# show me each currently running test
# it's not the same as running the tests in the verbose mode
% t/SMOKE -verbose
# run t/TEST, but show any problems after *each* tests is run
# useful for bug reports (it actually runs t/TEST -start, then
# t/TEST -run for each test separately and finally t/TEST -stop
% t/SMOKE -bug_mode
# now read the created report file
DESCRIPTION
The Problem
When we try to test a stateless machine (i.e. all tests are independent), running all tests once ensures that all tested things properly
work. However when a state machine is tested (i.e. where a run of one test may influence another test) it's not enough to run all the tests
once to know that the tested features actually work. It's quite possible that if the same tests are run in a different order and/or
repeated a few times, some tests may fail. This usually happens when some tests don't restore the system under test to its pristine state
at the end of the run, which may influence other tests which rely on the fact that they start on pristine state, when in fact it's not true
anymore. In fact it's possible that a single test may fail when run twice or three times in a sequence.
The Solution
To reduce the possibility of such dependency errors, it's helpful to run random testing repeated many times with many different srand
seeds. Of course if no failures get spotted that doesn't mean that there are no tests inter-dependencies, which may cause a failure in
production. But random testing definitely helps to spot many problems and can give better test coverage.
Resolving Sequence Problems
When this kind of testing is used and a failure is detected there are two problems:
1. First is to be able to reproduce the problem so if we think we fixed it, we could verify the fix. This one is easy, just remember the
sequence of tests run till the failed test and rerun the same sequence once again after the problem has been fixed.
2. Second is to be able to understand the cause of the problem. If during the random test the failure has happened after running 400
tests, how can we possibly know which previously running tests has caused to the failure of the test 401. Chances are that most of the
tests were clean and don't have inter-dependency problem. Therefore it'd be very helpful if we could reduce the long sequence to a
minimum. Preferably 1 or 2 tests. That's when we can try to understand the cause of the detected problem.
This utility attempts to solve both problems, and at the end of each iteration print a minimal sequence of tests causing to a failure. This
doesn't always succeed, but works in many cases.
This utility:
1. Runs the tests randomly until the first failure is detected. Or non-randomly if the option -order is set to repeat or rotate.
2. Then it tries to reduce that sequence of tests to a minimum, and this sequence still causes to the same failure.
3. (XXX: todo): then it reruns the minimal sequence in the verbose mode and saves the output.
4. It reports all the successful reductions as it goes to STDOUT and report file of the format: smoke-report-<date>.txt.
In addition the systems build parameters are logged into the report file, so the detected problems could be reproduced.
5. Goto 1 and run again using a new random seed, which potentially should detect different failures.
Reduction Algorithm
Currently for each reduction path, the following reduction algorithms get applied:
1. Binary search: first try the upper half then the lower.
2. Random window: randomize the left item, then the right item and return the items between these two points.
t/SMOKE.PL
t/SMOKE.PL is driving this module, if you don't have it, create it:
#!perl
use strict;
use warnings FATAL => 'all';
use FindBin;
use lib "$FindBin::Bin/../Apache-Test/lib";
use lib "$FindBin::Bin/../lib";
use Apache::TestSmoke ();
Apache::TestSmoke->new(@ARGV)->run;
usually Makefile.PL converts it into t/SMOKE while adjusting the perl path, but you create t/SMOKE in first place as well.
AUTHOR
Stas Bekman
perl v5.16.2 2011-02-07 Apache::TestSmoke(3)