Commandline 101: Getting a Grip on Grep

FAIL (the browser should render some flash content, not this).

This is Tech Tip Video Contest Week (March 9 - 13) at LinuxJournal.com!

Want a free 1-year digital subscription to Linux Journal? This is your lucky week. Watch the daily Tech Tip videos this week and collect the secret letters hosts Shawn Powers and/or Mitch Frazier announce during the videos each day. Come this Friday, unscramble the letters to reveal the secret word(s). Everyone with the correct answer who responds by 11:59:59PM U.S. Eastern Daylight Time March, Friday 13th, 2009 wins a free digital subscription to Linux Journal -- it's that easy!

Follow this link for further contest details, and good luck!

Download in .ogv format

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

please use pgrep, pkill

Anonymous's picture

Please use
pgrep
instead of
ps aux | grep [s]omething

The same with pkill

Thanks

Just examples

Shawn Powers's picture

I was just thinking of quick examples for the uses of grep. But thanks for the pgrep/pkill tips. :)

Shawn Powers is an Associate Editor for Linux Journal. You might find him chatting on the IRC channel, or Twitter

Webcast
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.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions