Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is there a faster way to search for a file containing a given string than using grep -re "string" /
This takes a long time to search through the entire system, so I was wondering if there is a faster way. I don't know the name of the file, just that it will contain a given string.
Look at the find command (info find) and the locate command (info locate). The locate is faster since it uses the data base of file names and locations so it doesn't have to read the drive for file names. On the other hand, find lets you filter the files by type, so you could limit the searching to files that, for example, are not executable or that were in system directories.
In fact, running grep -ar <expession> / may cause an infinite wait since it will eventually search /dev/null or /dev/random, and those (pseudo) files are infinitely long.
Look at the find command (info find) and the locate command (info locate). The locate is faster since it uses the data base of file names and locations so it doesn't have to read the drive for file names. On the other hand, find lets you filter the files by type, so you could limit the searching to files that, for example, are not executable or that were in system directories.
In fact, running grep -ar <expession> / may cause an infinite wait since it will eventually search /dev/null or /dev/random, and those (pseudo) files are infinitely long.
Thanks for the reply, but as far as I know, locate and find only search by file name, not the contents of the file? I don't know the name of the file or type, just that it contains a certain string on the inside...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.