ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Just something you might want to consider since you plan for it to search your whole filesystem which could be a lot of files.
The find command is gonna start a fgrep process for each file it finds and then look through it and then the fgrep process will close again. It's gonna repeat this till it's gone through each file it's found.
If you use the xargs command then a whole list of files can be sent to one fgrep process which reduces the overhead of having to stop and start so many processes. Ofcourse you get the added overhead of xargs and the pipe, but that's a lot less.
The nice thing about *nix is that it's good with handling starting and stopping of processes so you don't notice it that much. But if you try to run the same thing on Windows NT with cygwin then you really start noticing the difference, if it doesn't lock up on you in the mean time.
Anyways here is what the command with xargs would look like, which in my opinion also looks a lot simpler: