10-20-2009
and code behind ';' is never executed ???
and why do you mean it is too late ? i declaret it before it porcess row. If I am wrong correct me
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have written many awk commands which go in multiple lines.
I have this confusion many times.
Some time they work if i dont terminate them with "\" but some time error.
Some time in "if" statements between if and else if i dont use ";" it gives error but sometimes it doesnt.
The below... (4 Replies)
Discussion started by: pinnacle
4 Replies
2. Shell Programming and Scripting
I don't get correct output when I run this command line:
nmap -sP failedhost.com | grep -i failed | awk -F '{print $6}'
I basically want it to return 'failedhost.com' but its just showing the output of the nmap scan. (8 Replies)
Discussion started by: streetfighter2
8 Replies
3. UNIX for Dummies Questions & Answers
Little bit confusing while using awk :confused::confused:
In Sed while pattern search we can use "(double quotes)
i mean
$a=hello
$cat file.txt |sed -n "/$a/p"this thing work fine But if i use it in awk it's not working How could i do the substitution of pattern by a variables and the... (1 Reply)
Discussion started by: posix
1 Replies
4. Shell Programming and Scripting
i have a ksh code that needs to be written in AWK. can someone please help me here? :(
if }" | grep -c "$2") -gt 0 ] ; then
print - "found $2 in array ignore"
else
print - "did not find $2 in array ignore"
fi
ignore=4ty56r
ignore=er45ty
.
.
.
ignore=frhtg2 (27 Replies)
Discussion started by: usustarr
27 Replies
5. AIX
I have a file which is comma separated and has quotes. I can use this command and
awk -F"," '{ if ($4=="01" print $0 }' test.txt
But this doesn't fetch me the data.since it has quotes.
If the data has no quotes,the above command works fine.
In Unix you can skip quote \" but this doesn't work.... (7 Replies)
Discussion started by: ganesnar
7 Replies
6. Shell Programming and Scripting
Hi I have a bash file which will split a big file to many small files.
But I got a syntax error.H="$(head -1 CCC.tped)"
awk 'print $0 > $1 ".tped"' CCC.tped
for f in $(ls *.tped); do echo "$H\n" "$(cat $f)" >$f; done
And
-bash-4.1$ bash split
awk: print $0 > $1".tped"
awk: ^ syntax error... (3 Replies)
Discussion started by: zhshqzyc
3 Replies
7. Shell Programming and Scripting
Hi, I would like to know what is the correct syntax to perform a function in awk. Although I have seen several examples, not get it to work, this is what I'm trying:
#!/bin/bash
awk
function multi (number) {
return number * 3
}
print multi (4)Thanks (2 Replies)
Discussion started by: Godie
2 Replies
8. Shell Programming and Scripting
Hello,
I have perl script,which take some part of data in the file.
the below command works fine in normal cmd prompt.
`awk '/CDI/ && // && !/Result for/ {print $3 $5 > "final.txt"}' datalist.txt`;
`nawk -F"" '{print $2}' finalcdi.txt`;
But not working.
Please use code tags, thanks. (5 Replies)
Discussion started by: rasingraj
5 Replies
9. Shell Programming and Scripting
Hello Experts:
While writing a script to help one of the posts on here, I end up writing a wrong one. I am very much eager to know how this can be corrected.
Aim was to not print specified columns - lets say out of 100 fields, need to print all but 5th, 10th, 15th columns.
Someone already... (13 Replies)
Discussion started by: juzz4fun
13 Replies
10. Shell Programming and Scripting
awk -F, ' NR>1 {
BEGIN{
chr=$2
}
END{
for (k in chr) {print k}
}
} ' $gene_file
I've a really simple code. I want to store gene name and it's chromosome and in the end print them.
I'm skipping line one as it contains headers.
But I don't know why I get error as: (2 Replies)
Discussion started by: genome
2 Replies
cd(1) General Commands Manual cd(1)
NAME
cd - change working directory
SYNOPSIS
[directory]
DESCRIPTION
If directory is not specified, the value of shell parameter is used as the new working directory. If directory specifies a complete path
starting with or directory becomes the new working directory. If neither case applies, tries to find the designated directory relative to
one of the paths specified by the shell variable. has the same syntax as, and similar semantics to, the shell variable. must have execute
(search) permission in directory.
exists only as a shell built-in command because a new process is created whenever a command is executed, making useless if written and pro-
cessed as a normal system command. Moreover, different shells provide different implementations of as a built-in utility. Features of as
described here may not be supported by all the shells. Refer to individual shell manual entries for differences.
If is called in a subshell or a separate utility execution environment such as:
(which invokes on accessible directories) does not affect the current directory of the caller's environment. Another usage of as a stand-
alone command is to obtain the exit status of the command.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multi-byte character code sets are supported.
Environment Variables
The following environment variables affect the execution of
The name of the home directory,
used when no directory operand is specified.
A colon-separated list of pathnames that refer to directories.
If the directory operand does not begin with a slash character, and the first component is not dot or dot-dot, searches
for directory relative to each directory named in the variable, in the order listed. The new working directory is set
to the first matching directory found. An empty string in place of a directory pathname represents the current direc-
tory. If is not set, it is treated as if it was an empty string.
EXAMPLES
Change the current working directory to the directory from any location in the file system:
Change to new current working directory residing in the current directory:
or
Change to directory residing in the current directory's parent directory:
Change to the directory whose absolute pathname is
Change to the directory relative to home directory:
RETURN VALUE
Upon completion, exits with one of the following values:
The directory was successfully changed.
An error occurred. The working directory remains unchanged.
SEE ALSO
csh(1), pwd(1), ksh(1), sh-posix(1), sh(1), chdir(2).
STANDARDS CONFORMANCE
cd(1)