Tech Tip: Fun With Gawk
When grep and sed aren't enough, gawk may provide the extra horsepower that you need. The following tip contains a sampling of some of the things one might do with gawk.
Extract the last column from a text file, whitespace-separated:
cat myfile | gawk '{print $NF}'
or:
gawk '{print $NF}' myfile
List counts of files owned by each user in the current directory:
/bin/ls -l | \
gawk 'NR > 1 {counts[$3]++;}
END {for (s in counts) {
printf(" %-15s : % 5d\n",
s, counts[s]);}}' | \
sort
Kill your processes (one use is to kill a hung login if you can remotely log in to the workstation from another machine):
ps -elf | \
gawk -v me="$USER" '$3 == me {print $4}' | \
egrep -v $$ | \
xargs -i@@ kill -9 @@; kill -9 $$
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.
Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.
Sponsored by ActiveState
| Speed Up Your Web Site with Varnish | Jun 19, 2013 |
| Non-Linux FOSS: libnotify, OS X Style | Jun 18, 2013 |
| Containers—Not Virtual Machines—Are the Future Cloud | Jun 17, 2013 |
| Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer | Jun 12, 2013 |
| Weechat, Irssi's Little Brother | Jun 11, 2013 |
| One Tail Just Isn't Enough | Jun 07, 2013 |
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- Non-Linux FOSS: libnotify, OS X Style
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- RSS Feeds
- It is quiet helping
1 hour 41 min ago - Technology
1 hour 58 min ago - Reachli - Amplifying your
3 hours 14 min ago - excellent
4 hours 3 min ago - good point!
4 hours 6 min ago - Varnish works!
4 hours 15 min ago - Reply to comment | Linux Journal
4 hours 45 min ago - Reply to comment | Linux Journal
7 hours 11 min ago - Reply to comment | Linux Journal
11 hours 10 min ago - Yeah, user namespaces are
12 hours 27 min ago
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
thanks
Thanks for the tips, especially pkill (which is new with Solaris 7; 1998! :) ).
The file count routine I use for counting source files in the current directory, so strange filenames are not an issue (also I find find to be kind of slow).
Here is the online manual for gawk: http://www.gnu.org/software/gawk/manual/
Here is a little program people might remember coding from FORTRAN class; maybe it can help put the baby to sleep:
echo 100 1 10 0.01 | gawk '{amp = $1; freq = $2; cycles = $3; tdelta = $4; for (i = 0; i <= 2 * 3.14159 * cycles; i += 2 * 3.14159 / 360) {printf("%*s\n", int((amp/2.0) * sin(i * freq) + (amp/2.0)), "*"); system("sleep " tdelta); }}'
What does this have to do
What does this have to do with Fortran? I use Fortran every day, and have no idea what you're talking about. Also, I was born in '84, long after punch cards and FORTRAN IV etc., which may explain my confusion.
don't parse output of ls
Too many odd things can be in file names, spaces, newlines, etc.
It's a rare case that all you want is a list of file names. In most cases you want to do something to the files based on their names, and if that's the case, 'find' can be a better tool, or maybe ' stat -c %n [glob]'.
Start learning basic unix commands before playing with awk
Sorry, but there is no need to use (g)awk here. I really like (g)awk, but your examples are just poor. Ok, maybe first one is a typical case for awk.
You forgot about dot files, but second one can be replaced with:
ls -Al | sed '1d;s/\([^ \t]\+[ \t]\+\)\{2\}//;s/[ \t].*//' | sort | uniq -cor even better:
Third one (really badly and also wrongly implemented) is a perfect case for pkill:
I can agree that your second example might be faster than mine, but it's irrelevant here.
Regards.