|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Proxy ARP Difficulties | TheMaskedMan | IP Networking | 7 | 11-02-2005 06:14 AM |
| Simple Network Program Difficulties | Mistwolf | High Level Programming | 2 | 03-19-2002 02:34 AM |
 |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
05-11-2008
|
||||
|
||||
|
Admitted that rubin's way is much more clearer and readable, you can pass variables also interrupting and resuming the awk code by the means of single quotes, like I posted before.
The problem is that before I made a mistake, you also need to add a couple of double quotes to complicate things a little bit more  Code:
awk '$3=="'"$MONTH"'" {print $1, $2, $3, $4, $5, $6}' *.hits
|
| Forum Sponsor | ||
|
|
|
05-11-2008
|
||||
|
||||
|
Here goes another unconventional way of passing variables to awk:
Code:
echo "Enter month: "
read MONTH
awk '/'$MONTH'/ { print ... }' file
The above approach does not work if the variable has whitespaces, newlines or certain special characters ( |, /, ...) in it. So it's always recommended using the conventional way -v var=... . Last edited by rubin; 05-11-2008 at 02:21 PM. Reason: last sentence
|
||||
| Google The UNIX and Linux Forums |
Linear Mode
