Sponsored Content
Full Discussion: Awk if elseif syntax error
Top Forums Shell Programming and Scripting Awk if elseif syntax error Post 302317249 by vgersh99 on Monday 18th of May 2009 11:28:55 AM
Old 05-18-2009
  1. 'elseif' is a not a valid awk statement
  2. For matching regex use '~'
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

awk syntax error

can anyone see the awk syntax error near line 1? I keep getting this error and I'm not familiar with awk very well yet so it is hard for me to see the errors. fyi: deleteuser* refers to files in the directory where each one ends with a different date ls -1 /mfupload/prod02/ftp/deleteuser* |... (12 Replies)
Discussion started by: k@ssidy
12 Replies

2. Shell Programming and Scripting

awk syntax error

mVar=0 count=`awk -F, '( ( $2 ~ /^GIVEUP$/ && $3 ~ /^NEW$/ ) || ( $2 ~ /^SPLIT$/ && $3 ~ /^NEW$/ ) || ( $2 ~ /^OPTION$/ && $3 ~ /^NEW$/ ) || ( $2 ~ /^OPTIONSPLIT$/ && $3 ~ /^NEW$/ ) ) { count++ } END { print count }' myCSV.csv myVar=`expr $myVar + $count` Can I do this? I get a syntax... (4 Replies)
Discussion started by: yongho
4 Replies

3. Shell Programming and Scripting

syntax error with awk.

A shell script a.sh calls an awk script using : awk -v OUTPUTDIR=${OUTPUTDIR}${OUTPUTDIRDATE} -f ${SCRIPTSPATH}chngNullBillId.awk ${INPUTFILE} chngNullBillId.awk : { if (substr($0,9,4)=="0000") printf( "%s0001%s", substr($0,1,8), substr($0,13,67) )>>${OUTPUTDIR}"goodfile.txt"; else print... (2 Replies)
Discussion started by: Amruta Pitkar
2 Replies

4. UNIX for Dummies Questions & Answers

'awk' syntax error

Due to some syntax error, my below code is not working. #!/usr/bin/ksh nawk ' BEGIN { cur_val=0; cur_zero=0; cur_nine=0; sum_zero=0; sum_nine=0; } /^/ { cur_val=substr($0,5,2); if("cur_val" == "0") { ... (3 Replies)
Discussion started by: lokiman
3 Replies

5. UNIX for Dummies Questions & Answers

awk syntax error

I generate a fullpath variable two different ways: 1) concat two variables rootpath and relpath to give me fullpath 2) use 'find' to get the fullpath when I echo the variable, I get the same output for both. However, I print the variable from method 1 in the below loop I get "awk syntax... (0 Replies)
Discussion started by: orahi001
0 Replies

6. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies

7. Shell Programming and Scripting

awk syntax error

Hi, I can't see what is wrong with the following command. I am extracting a dollar amount (AMT_REJ, 6th field) from a comma delimited record and need to output it as numeric, removing the $sign and decimal point and output to another file. Everything seems to work except the $ sign which I need... (1 Reply)
Discussion started by: ski
1 Replies

8. Shell Programming and Scripting

Syntax error using Awk

more report2.txt how to modify the AWK to print above out put for given n no of inputs using report2.txt file? out put should be (3 Replies)
Discussion started by: kanakaraju
3 Replies

9. UNIX for Dummies Questions & Answers

If Then ElseIf Script - Confusion Around Expression's Syntax

Hello, I am relatively new to UNIX scripting and am learning a lot. I have already tried several searches on this website and have tried various syntax options suggested to no avail. I am obviously not writing the script correctly. I really do appreciate any and all the help. Below is an... (8 Replies)
Discussion started by: dqrgk0
8 Replies

10. Shell Programming and Scripting

awk syntax error

Hi All, I wrote a simple script.sh program for i in seq (22) do awk '$1==${i}' file1.txt|awk '{print $2}'> file${i}_study.txt done and then run it %bash %chmod +x script.sh % ./script.sh Give me error awk: $1==${i} awk: ^ syntax error Do you have any idea why... (3 Replies)
Discussion started by: senayasma
3 Replies
packingrules(4) 					     Kernel Interfaces Manual						   packingrules(4)

NAME
packingrules - packing rules file for cachefs DESCRIPTION
is a packing rules file for packingrules contains a list of directories and files that are to be packed. It also contains a list of direc- tories and files that are to be specifically excluded from packing. See cachefspack(1M). Many users choose to manually create the packing rules file and edit it by hand. Users can edit the packingrules (using any editor) to permanently change the packingrules file, or to gain access to more powerful options that are not available from the command line (such as the command). It is much easier to enter complex wildcard expressions by editing the packingrules file. Following is a description of the lines in a packing rules file. Blank lines and lines that begin with a pound sign are ignored. Lines can be continued by placing a backslash () immediately before the newline character. All other lines in the packingrules file have one of the following formats: This line identifies a directory (or pair of directories) under which files should be packed. At least one directory name must be specified. The arguments must be fully qualified path names and may include environment variables. This line enumerates a list of files and subdirectories beneath the current directory to be packed. This specification is recursive. That is, specifying the name of a directory automatically includes all files and subdirectories it contains. This line enumerates a list of files that are not to be packed. Regular expressions are permitted. There are important differences between the arguments to the and the statements. The arguments to statements can contain slashes and are interpreted as file names relative to the directories. The arguments to statements are simpler names or expressions that cannot contain slashes. An statement will not override a LIST statement. statements only exclude files that are found beneath listed directories. If the first name argument to a or an statement begins with an exclamation point the remainder of the statement will be executed as a com- mand that will be run in the current directory. The output of the command will be treated as a list of newline separated file names to be packed command) or to be excluded from the packing list command). For the command, the resulting file names will be interpreted relative to the enclosing directory. Blanks can be embedded in an argument by escaping them with a backslash () or enclosing the argument in double quotes (` " '). Double quotes can be passed in arguments by escaping the double quotes with a backslash (). lines only apply to the statement that precedes them. lines can appear before any statement (in which case they apply to all or after a statement (in which case they only apply to the that precedes them). Any number of these statements can occur in any combinations. The order is not important. EXAMPLES
The use of these statements is illustrated in the following packing rules file. # # Ignore junk files. # IGNORE core *.o *.bak *% # # Pack everything in the work subdirectory and in a few # favorite mailboxes. # BASE /net/bigserver/export/home/myname LIST work LIST m/incoming LIST m/action LIST m/pending # # Pack two important project directories but skip # all postscript output. # BASE /net/bigserver/export/projects $HOME/projects LIST poindexter epiphany IGNORE *.ps # # Pack the foonly package. # BASE /net/bigserver/opt/foonly /opt/foonly LIST !cat .packinglist # # Also pack the latest executables for the standard # build environment. # BASE /net/bigserver/export/buildenv $HOME/buildenv LIST !find . -type f -a -perm -111 -a -print AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
cachefspack(1M). packingrules(4)
All times are GMT -4. The time now is 07:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy