The for i in {1..3} works in some shells, but not others. Since the first line of your script doesn't specify what shell you want, it will run using your system's default shell. Then $i in your awk command will not be an expansion of your shell variable; it will reference $0 (the entire input line) since the variable i in your awk script is undefined.
You could try something like:
If you want to try this on a Solaris/SunOS system, use /usr/xpg4/bin/awk, /usr/xpg6/bin/awk, or nawk instead of awk.
Note that this script call awk once (no matter how many lines are in file2.txt) rather than calling awk twice and paste once for each line in file2.txt.
This User Gave Thanks to Don Cragun For This Post:
Hi guys,
I need help in extracting one column of numbers from two different files and display it in a output file. In specific, I want to extrac the column no.2 ($2) from each file, file1.txt, file2.txt. Then place both extracted columns in a one file, out.txt.
the line command I use to... (7 Replies)
Suppose i have a file A
1*2*3*4
2*4*4*22
and second file B
2*3*4*5
4*4*6*7
By multiplying file A by file B that is file A by first column in file B respectively
output shud be
2*6*12*20
8*16*24*154
my code is
=$1
next
}
{for (f=1;f<=NF;f++) (2 Replies)
Hi,
i have file1 which looks like:
x1 y1 z1
x2 y2 z2
...(and so on)
and file2 which looks like:
a11 a12 a13
a21 a22 a23
a31 a32 a33
and i want to replace file1 with the following values:
x1' y1' z1'
x2' y2' z2'
...(and so on) (2 Replies)
Hi,
This is something that probably it is more difficult to explain than to do.
I have two files e.g.
FILE1
A15 8.3102E+00 3.2000E-04
A15 8.5688E+00 4.3000E-05
B13 5.1100E-01 1.9960E+00
B16 5.1100E-01 2.3000E-03
B16 8.6770E-01 1.0000E-07
B16 9.8693E-01 3.4000E-05... (4 Replies)
Hi,
I have 2 ASCII files, say
file1
AAAAA 3.465830E-12
BBBBB 4.263280E-08
CCCCC 1.113320E-17
DDDDD 0.000000E+00
...
file2 with as many lines as file1
3.932350E-12
1.194380E-07
4.901480E-17
0.000000E+00
3.921180E-40 (3 Replies)
I need to multiply column1 and column3 data and need to compare it with column5. Need to check multiplication and Throw error if result is greater or less than column5 values, though difference of +/- 2 will be ok
Ex - if column1 has 2.4 and column3 has 3.5, it will be ok if column5 have value... (13 Replies)
Example:
I have files in below format
file 1:
zxc,133,joe@example.com
cst,222,xyz@example1.com
File 2 Contains:
hxd
hcd
jws
zxc
cst
File 1 has 50000 lines and file 2 has around 30000 lines :
Expected Output has to be :
hxd
hcd
jws (5 Replies)
Discussion started by: TestPractice
5 Replies
LEARN ABOUT DEBIAN
apsfilter-bug
APSFILTER-BUG(1) BSD General Commands Manual APSFILTER-BUG(1)NAME
apsfilter-bug -- create a half-automatic bug report for apsfilter
SYNOPSIS
apsfilter-bug
OPTIONS
none
DESCRIPTION
With the apsfilter-bug script you can automatically create a bug report for apsfilter(1). A template report file is created which you can
edit with your favourite editor ( emacs(1) by default, or whatever is entered in the environment variable EDITOR ).
You will see a couple of lines starting with '#'; these lines will be removed before the report is sent. So if you want to use the '#' char-
acter at the beginning of a line, just indent it with a space.
A very important piece of the bug report is the debugging log created by aps2file(1), probably with a command like
aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
Unless you don't even have a chance to create a debugging log, it is crucial for serious bug hunting.
After you have filled in as much (useful) information as possible, you must save the file under its original name, then exit your editor.
If you invoked apsfilter-bug by accident, or if you need some additional system information to include into the bug report, just exit your
editor without saving the file.
NOTES
In addition to the stuff you've edited, some more information is appended to the bug report automatically:
apsfilter version 7.2.6-stable
ghostscript version (from 'gs --version')
system id (from 'uname -a')
configure options --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-awk=/usr/bin/awk --with-sendmail=/usr/sbin/sendmail
shell executable /bin/bash
awk executable /usr/bin/awk
sendmail executable /usr/sbin/sendmail
FILES
/usr/bin/aps2file script to create debugging output
SEE ALSO apsfilter(1), aps2file(1)BUGS
See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.
Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which
asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via e-mail to the proper
apsfilter mailinglist.
If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save
the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug
and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the
mail to the apsfilter mailinglist.
Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works.
Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing /bin/sh or
bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).
DOCUMENTATION
See official apsfilter homepage
http://www.apsfilter.org/handbook.html Apsfilter Handbook including the Frequently Asked Questions (FAQ)
USER FORUM
Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.org. The above section BUGS and the file
HOWTO-BUGREPORTS tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage
aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.
HISTORY
The apsfilter-bug manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.
BSD Dec 26, 2001 BSD