09-28-2004
I doubt that the error is where you think it is. Ignore the line numbers. There are two ways to find something like this.
1 search for each ( since one of them follows something wrong.
2 copy the script to a temp file. Run the temp file and reproduce the error. Now pull some stuff out...for example, remove the nawk statements and replace them with "echo nawk went here. Remove a little at a time and try to run the script after each removal. You just need to reach the point where the shell can parse the script. It's ok that the script can't do anything useful after you remove stuff.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I found a command who prints x lines before and after a line who contain a searched string in a text file.
The command is :
-------------------
nawk 'c-->0;$0~s{if(b)for(c=b+1;c>1;c--)print r;print;c=a}b{r=$0}' b=2 a=4 s="string" file1
...where "b" and "a" are the number of lines to print... (2 Replies)
Discussion started by: ctap
2 Replies
2. 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
3. Shell Programming and Scripting
What am I doing wrong here? I get syntax error.
I am trying to parse a file looking for the lines with "running" as the first field then print the 5th field, then looking at the 9th field for specific values and writing the whole line to a junk file.
nawk ';
{if ($1 == "running")... (10 Replies)
Discussion started by: beppler
10 Replies
4. Shell Programming and Scripting
Hi Gurus,
I am using a script as under :
read string
nawk -v search="$string" '
/a/,/z/ {
block = (block ? block ORS : "") $0;
}
/z/ {
if (block ~ search)
print block;
} ' <File>
nawk -v search="$string" '
/b/,/z/ {
... (1 Reply)
Discussion started by: vanand420
1 Replies
5. Shell Programming and Scripting
hi people;
this is my two awk code:
nawk '/cell+-/{r=(NF==8) ? $4FS$5FS$6 : NF==7 ? $4FS$5 : $4 ;c=split(r,rr);for (i=1;i<=c;i++){if(rr != "111111"){printf($3" %d ""\n",(i+3))}}printf("")}' /home/gc_sw/str.txt > /home/gc_sw/predwn.txt
nawk -F'*' '{gsub(/ *$/,"")}$0=$1$($NF-2)'... (2 Replies)
Discussion started by: gc_sw
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
Please help me I want to filter all messages having a value less than a particular value..Please advice how to use <= in the below red marked script..
Getting the error as no such file or directory for the marked line no.
Thanks in advance...
Script is as under :
read message
gawk... (5 Replies)
Discussion started by: vanand420
5 Replies
7. Shell Programming and Scripting
help out with code. two files aaa bbb contains some records..output file xyz should be like this..see below
i/p file:aaa
08350|60521|0000|505|0000|1555|000|NYCMT|Pd_1 |-11878
i/p file: bbb
60521|60510
o/p file :xyz
60510|08350|60521|0000|505|0000|1555|000|NYCMT|Pd_1 |-11878 (5 Replies)
Discussion started by: Diddy
5 Replies
8. Shell Programming and Scripting
hi guys,
I am writing a code and have stuck at one point. Inside nawk I am storing my desired variable a, I just need to find if a is present in an external file error.log or not. If yes, print something. grep or for loop not working properly inside nawk. Sample code provided.
nawk '
BEGIN... (5 Replies)
Discussion started by: shekhar2010us
5 Replies
9. Shell Programming and Scripting
I don't know whats wrong with the code here.
Its giving double counts.
nawk -F# '
{
if( match($2, "= ") > 0)
num=substr($2,RSTART+2,length($2)-1);
if (match($20, "= ") > 0)
res=substr($20,RSTART+2,length($20)-1);
if(match(num,... (2 Replies)
Discussion started by: jagpreetc
2 Replies
10. Shell Programming and Scripting
Hi.. i am running nawk scripts on solaris system to get records of file1 not in file2 and find duplicate records in a while with the following scripts -compare
nawk 'NR==FNR{a++;next;} !a {print"line"FNR $0}' file1 file2duplicate - nawk '{a++}END{for(i in a){if(a-1)print i,a}}' file1in the middle... (12 Replies)
Discussion started by: Abhiraj Singh
12 Replies
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-akq] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command is given, script will run the specified command with an optional argument vector instead of an interactive shell.
The following options are available:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time
Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-D (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variable is utilized by script:
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO
csh(1) (for the history mechanism).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD
January 22, 2004 BSD