01-20-2006
The FNR variable contains the number of lines read, but is reset for each file read. The NR variable accumulates for all files read. Therefore if you execute an awk script with two files as arguments, with each containing 10 lines:
nawk '{print NR}' file file2
nawk '{print FNR}' file file2
the first program would print the numbers 1 through 20, while the second would print the numbers 1 through 10 twice, once for each file.
printf is used to print the output into the file instead of screen. inside the printf %s is used for string printing and %c is used for character printing. that is $0 as string and OFS is out field separator as character other then space which is default.
10 More Discussions You Might Find Interesting
1. Programming
Where can a locate a list of Unix exit codes?
thank you,
Donna (3 Replies)
Discussion started by: donna carter
3 Replies
2. UNIX for Dummies Questions & Answers
I have the below script I am running on a Solaris system to check the status of a Tivoli Workload Scheduler job and return the status. We need this script to return a '0' if any of the jobs in the stream are in a "EXEC" state and an "1" if in a "HOLD" state. I am not a programmer so I am not sure... (1 Reply)
Discussion started by: leezer1204
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Can anyone tell me if there are return codes for SFTP? If so how would you capture them? I've tried 'man sftp' but its not particularly helpful.
Many thanks
Helen :confused: (4 Replies)
Discussion started by: Bab00shka
4 Replies
4. UNIX for Advanced & Expert Users
Know any good codes? (2 Replies)
Discussion started by: fgjiu
2 Replies
5. UNIX for Advanced & Expert Users
I have a simple script which renames a file.How do i capture the return code of the script if the script fails (3 Replies)
Discussion started by: kris01752
3 Replies
6. Shell Programming and Scripting
Hi
In an unix script I am using an Perl one liner perl -i -ne '-----'
If the perl one liner fails i am not able to catch the return code.
It always give 0 as return code. Can you tell me how can i catch the return code
perl -i -ne '---'
RETCODE=$?
echo $RETCODE
Thanks and Regards
Ammu (2 Replies)
Discussion started by: ammu
2 Replies
7. Shell Programming and Scripting
Good Morning All..
I was wondering about getting exit codes of a command in a shell script. I'm trying to run uvscan (McAfee command line scanner) and I want to have the log file say why, if at all, the process failed/exited.
Something to the extent of
If ; then
echo "This is why it... (1 Reply)
Discussion started by: cmschube
1 Replies
8. AIX
Dear Experts,
i am very to AIX when i am trying to compile my code i am getting two warning several times like
1540-0053 (W) The declaration of a class member within the class definition must not be qualified.
"/usr/include/alloca.h", line 34.9: 1540-1401 (I) An unknown "pragma __alloca" is... (1 Reply)
Discussion started by: vin_pll
1 Replies
9. Linux
I am trying to run this SH on Linux and getting error at IF condition.
I want to read the EXIT code and send the failure or success message.
Please help me on this. This worked when i was running on Solaris.
#!/bin/bash
$ORACLE_HOME/bin/sqlplus abc/xyz@qwe @/home/test.sql
if ;... (4 Replies)
Discussion started by: rlmadhav
4 Replies
10. UNIX for Dummies Questions & Answers
Not sure if this is of any use but......
I was messing around with getting return codes greater than 255 for special usage...
Of course the code could be made simple but in this code the new stored return code
is generated as exit is progressing...
#!/bin/sh
# Real and imaginary return... (9 Replies)
Discussion started by: wisecracker
9 Replies
LEARN ABOUT OPENDARWIN
cat
CAT(1) BSD General Commands Manual CAT(1)
NAME
cat -- concatenate and print files
SYNOPSIS
cat [-benstuv] [file ...]
DESCRIPTION
The cat utility reads files sequentially, writing them to the standard output. The file operands are processed in command-line order. If
file is a single dash ('-') or absent, cat reads from the standard input. If file is a UNIX domain socket, cat connects to it and then reads
it until EOF. This complements the UNIX domain binding capability available in inetd(8).
The options are as follows:
-b Number the non-blank output lines, starting at 1.
-e Display non-printing characters (see the -v option), and display a dollar sign ('$') at the end of each line.
-n Number the output lines, starting at 1.
-s Squeeze multiple adjacent empty lines, causing the output to be single spaced.
-t Display non-printing characters (see the -v option), and display tab characters as '^I'.
-u The -u option guarantees that the output is unbuffered.
-v Display non-printing characters so they are visible. Control characters print as '^X' for control-X; the delete character (octal
0177) prints as '^?'. Non-ASCII characters (with the high bit set) are printed as 'M-' (for meta) followed by the character for the
low 7 bits.
DIAGNOSTICS
The cat utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The command:
cat file1
will print the contents of file1 to the standard output.
The command:
cat file1 file2 > file3
will sequentially print the contents of file1 and file2 to the file file3, truncating file3 if it already exists. See the manual page for
your shell (i.e., sh(1)) for more information on redirection.
The command:
cat file1 - file2 - file3
will print the contents of file1, print data it receives from the standard input until it receives an EOF ('^D') character, print the con-
tents of file2, read and output contents of the standard input again, then finally output the contents of file3. Note that if the standard
input referred to a file, the second dash on the command-line would have no effect, since the entire contents of the file would have already
been read and printed by cat when it encountered the first '-' operand.
SEE ALSO
head(1), more(1), pr(1), sh(1), tail(1), vis(1), zcat(1), setbuf(3)
Rob Pike, "UNIX Style, or cat -v Considered Harmful", USENIX Summer Conference Proceedings, 1983.
STANDARDS
The cat utility is compliant with the IEEE Std 1003.2-1992 (``POSIX.2'') specification.
The flags [-benstv] are extensions to the specification.
HISTORY
A cat utility appeared in Version 1 AT&T UNIX. Dennis Ritchie designed and wrote the first man page. It appears to have been cat(1).
BUGS
Because of the shell language mechanism used to perform output redirection, the command ``cat file1 file2 > file1'' will cause the original
data in file1 to be destroyed!
BSD
September 15, 2001 BSD