Create a hash, store first field as key and second field as value if key is found, otherwise, initialize the value an empty array. At the end, print the hash.
Let's say I write a simple script that contains the following:
date | awk '{print $1}'
date | awk '{print $2}'
Of course, when I run the script the output will look similar to:
Tue
Mar
What if I want my ouput to be on one line as follows:
Tue Mar
What changes would I need to... (2 Replies)
I have a file in CSV format (2 columns ID and Number of Items):
AB1 ,,10
AB2 ,,20
AB2 ,, 30
AB3 ,, 10
AB4 ,, 20
AB4 ,, 30
AB4 ,, 40
AB5 ,, 50
AB6 ,, 10
AB7 ,, 20
AB7 ,, 30
AB7 ,, 40
......
This file is produced daily i would like to get it in the following format, so... (6 Replies)
Hello,
I have got the following kine in my script
awk '{printf("%s,", $0);next}{printf("%s", $0)}' ORS="," a.txt > b.out
The contents of b looks somewaht like this:
QUEUE(QUEUE1.Q),CURDEPTH(0),QUEUE(QUEUE2.Q),CURDEPTH(0),QUEUE(QUEUE3.Q),CURDEPTH(0)
But my desired output is :... (10 Replies)
# echo $PATH
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
How would i write a script to display permission on each folders in $PATH variable below format.
drwxr-xr-x 2 0 root 4096 Nov 24 14:51 /usr/kerberos/sbin
drwxr-xr-x 2 0... (2 Replies)
Hi I have a file as given below:
<table border=1>
<TR><TH>Script Name</TH><TH>CVS Status</TH><TH>Script Location</TH></TR>
<TR><TD><CENTER>Work Area: /home/ustst/</CENTER></TD></TR>
<TR><TD><CENTER>admin_export.sh</CENTER></TD><TD><CENTER>Locally... (1 Reply)
Hi all,
Below is my testfile:
COST,31-MAR-2011 01:01:04,31-MAR-2011 11:22:12,622
COST,21-MAR-2011 22:00:20,22-MAR-2011 11:07:23,788
FARE,23-MAR-2011 22:00:22,24-MAR-2011 10:10:46,731
FARE,02-MAR-2011 14:01:50,03-MAR-2011 08:30:54,1110
I need to append a number, for example 700, to the... (2 Replies)
when i try this awk its giving out put as below.
awk '!(/^$/||/--/||/selected/||/^ *$/){print $1}' tmp.txt
output
=====
1
2010-08-03-12.31.26.126000
how excluede the 1st line ? i mean i want output only 2nd line i.e 2010-08-03-12.31.26.126000; (5 Replies)
Our vendor produces a report that I would like to format in a particular way.
Here is the sample output from their report:
# AA.INDEX 2 11 2 239 52 (7,2) 07 MAY 11 203.1 55
# ACCOUNT 2 89561 2 ... (4 Replies)
Hi all,
I'm writing a simple awk code:
awk 'BEGIN {FS="|"};{print "Type\tNumber\ttypes\tTotal";};{print $1, "\t", $2, "\t", $3, "\t", $4, "\t";}' db_query.txt
it gives me the result:
Type Number types Total
XXX 498.0 5100.0 5274.661
Type Number types Total... (7 Replies)
i would like to format the 9 character with suffix as "0".
i tried below it doesn't work.
>a=12345
> echo $a | awk '{printf "%-09s\n",$1}'
>12345
required output is 123450000
can you guys help me out ? (7 Replies)
Discussion started by: expert
7 Replies
LEARN ABOUT MOJAVE
test::use::ok
Test::use::ok(3) User Contributed Perl Documentation Test::use::ok(3)NAME
Test::use::ok - Alternative to Test::More::use_ok
SYNOPSIS
use ok 'Some::Module';
DESCRIPTION
According to the Test::More documentation, it is recommended to run "use_ok()" inside a "BEGIN" block, so functions are exported at
compile-time and prototypes are properly honored.
That is, instead of writing this:
use_ok( 'Some::Module' );
use_ok( 'Other::Module' );
One should write this:
BEGIN { use_ok( 'Some::Module' ); }
BEGIN { use_ok( 'Other::Module' ); }
However, people often either forget to add "BEGIN", or mistakenly group "use_ok" with other tests in a single "BEGIN" block, which can
create subtle differences in execution order.
With this module, simply change all "use_ok" in test scripts to "use ok", and they will be executed at "BEGIN" time. The explicit space
after "use" makes it clear that this is a single compile-time action.
SEE ALSO
Test::More
CC0 1.0 Universal
To the extent possible under law, XX has waived all copyright and related or neighboring rights to Test-use-ok.
This work is published from Taiwan.
<http://creativecommons.org/publicdomain/zero/1.0>
POD ERRORS
Hey! The above document had some coding errors, which are explained below:
Around line 45:
Non-ASCII character seen before =encoding in 'XX'. Assuming UTF-8
perl v5.18.2 2012-09-11 Test::use::ok(3)