Hi, I need to change military time to regular time. I know to use case to indicate whether a.m. or p.m. as follows:
case "$hour"
in
0? | 1 ) echo a.m.;;
1 ) echo p.m.;;
* ) echo p.m.;;
esac
My question is how do I add the hour and minute... (2 Replies)
Hi
I am wondering is it possible to combine two greps together
I have two greps.
grep "^,, *\." file
(grep the line which has a '.' in the third column)
grep "=" file
(grep the line which has = anywhere)
How to put them together so that if the content of the file that match either... (1 Reply)
Greetings!
I have been tasked to create a report off files we receive from our hardware suppliers. I need to grep these files for two fields 'Test_Version' and 'Model-Manufacturer' ; for each field, I need to capture their corresponding values.
When running each statement separately, I get... (4 Replies)
below is something i inherited:
if && && ; then
HOST_SELECT="-m quadcore"
fi
if && && ; then
HOST_SELECT="-m quadcore"
fi
if && && ; then
HOST_SELECT="-m octocore1"
fibelow is what i changed it to:
if && && ; then
HOST_SELECT="-m quadcore"... (2 Replies)
Hi,
I have the following two awk statements which I'd like to consolidate into one by piping the output from the first into the second awk statement (rather than having to write kat.txt out to a file and then reading back in).
awk 'BEGIN {FS=OFS=" "} {printf("%s ", $2);for (x=7; x<=10;... (3 Replies)
i have a datafile that has several lines that look like this:
2,dataflow,Sun Mar 17 16:50:01 2013,1363539001,2990,excelsheet,660,mortar,660,4
using the following command:
awk -F, '{$3=strftime("%a %b %d %T %Y,%s",$3)}1' OFS=, $DATAFILE | egrep -v "\-OLDISSUES," | ${AWK} "/${MONTH} ${DAY}... (7 Replies)
Hello again everyone,
yes, I'm back again for more help! So I'm attempting to read two separate files and generate some XML code from that. My current code is:
BEGIN {
print "<?xml version=\"1.0\" encoding=\"utf-8\">"
print "<Export>"
}
{
x=1;
print "<section name=\"Query" NR "\">"... (5 Replies)
Hello fellow awkers,
I am trying to combine the following awk statements into 1 so that the results are more accurate:
awk '/\=\+/ { count++ } END { print count}' filename
awk '/\=\?/ { count++ } END { print count}' filename
awk '/\=\-/ { count++ } END { print count}' filename
awk... (8 Replies)
Hi
What is the right structure to use awk with multiple If statements
The following code doesn't work
#
awk '
{
A = $1
}
END {
for ( i = 1; i <= c; i++ )
{
if ( A == 236 && A ==199... (7 Replies)
I have a file like
file.
file.TODAY.THISYEAR
file.TODAY.LASTYEARI want to substitute the words in caps with their actual values so that output should look like
file.140805
file.140805.2014
file.140805.2013For this I am reading the file line bye line in an array and using multiple map... (1 Reply)
Discussion started by: sam05121988
1 Replies
LEARN ABOUT MOJAVE
test::use::ok5.18
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)