How do I find all files containing specific text on Linux?


Linux Problem Overview

I'm trying to find a way to scan my entire Linux system for all files containing a specific string of text. Just to clarify, I'm looking for text within the file, not in the file name.

When I was looking up how to do this, I came across this solution twice:

find / -type f -exec grep -H 'text-to-find-here' {} \;

However, it doesn't work. It seems to display every single file in the system.

Is this close to the proper way to do it? If not, how should I? This ability to find text strings in files would be extraordinarily useful for some programming projects I'm doing.

Linux Solutions

Solution 1 - Linux

Do the following:

grep -rnw '/path/to/somewhere/' -e 'pattern'
  • -r or -R is recursive,
  • -n is line number, and
  • -w stands for match the whole word.
  • -l (lower-case L) can be added to just give the file name of matching files.
  • -e is the pattern used during the search

Along with these, --exclude, --include, --exclude-dir flags could be used for efficient searching:

  • This will only search through those files which have .c or .h extensions:
grep --include=\*.{c,h} -rnw '/path/to/somewhere/' -e "pattern"
  • This will exclude searching all the files ending with .o extension:
grep --exclude=\*.o -rnw '/path/to/somewhere/' -e "pattern"
  • For directories it's possible to exclude one or more directories using the --exclude-dir parameter. For example, this will exclude the dirs dir1/, dir2/ and all of them matching *.dst/:
grep --exclude-dir={dir1,dir2,*.dst} -rnw '/path/to/somewhere/' -e "pattern"

This works very well for me, to achieve almost the same purpose like yours.

For more options check man grep.

Solution 2 - Linux

You can use grep -ilR:

grep -Ril "text-to-find-here" /
  • i stands for ignore case (optional in your case).
  • R stands for recursive.
  • l stands for "show the file name, not the result itself".
  • / stands for starting at the root of your machine.

Solution 3 - Linux

You can use ack. It is like grep for source code. You can scan your entire file system with it.

Just do:

ack 'text-to-find-here'

In your root directory.

You can also use regular expressions, specify the filetype, etc.


I just discovered The Silver Searcher, which is like ack but 3-5x faster than it and even ignores patterns from a .gitignore file.

Solution 4 - Linux

You can use:

grep -r "string to be searched"  /path/to/dir

The r stands for recursive and so will search in the path specified and also its sub-directories. This will tell you the file name as well as print out the line in the file where the string appears.

Or a command similar to the one you are trying (example: ) for searching in all javascript files (*.js):

find . -name '*.js' -exec grep -i 'string to search for' {} \; -print

This will print the lines in the files where the text appears, but it does not print the file name.

In addition to this command, we can write this too: grep -rn "String to search" /path/to/directory/or/file -r: recursive search n: line number will be shown for matches

Solution 5 - Linux

You can use this:

grep -inr "Text" folder/to/be/searched/

Solution 6 - Linux

grep (GNU or BSD)

You can use grep tool to search recursively the current folder, like:

grep -r "class foo" .

Note: -r - Recursively search subdirectories.

You can also use globbing syntax to search within specific files such as:

grep "class foo" **/*.c

Note: By using globbing option (**), it scans all the files recursively with specific extension or pattern. To enable this syntax, run: shopt -s globstar. You may also use **/*.* for all files (excluding hidden and without extension) or any other pattern.

If you've the error that your argument is too long, consider narrowing down your search, or use find syntax instead such as:

find . -name "*.php" -execdir grep -nH --color=auto foo {} ';'

Alternatively, use ripgrep.


If you're working on larger projects or big files, you should use ripgrep instead, like:

rg "class foo" .

Checkout the docs, installation steps or source code on the GitHub project page.

It's much quicker than any other tool like GNU/BSD grep, ucg, ag, sift, ack, pt or similar, since it is built on top of Rust's regex engine which uses finite automata, SIMD and aggressive literal optimizations to make searching very fast.

It supports ignore patterns specified in .gitignore files, so a single file path can be matched against multiple glob patterns simultaneously.

You can use common parameters such as:

  • -i - Insensitive searching.

  • -I - Ignore the binary files.

  • -w - Search for the whole words (in the opposite of partial word matching).

  • -n - Show the line of your match.

  • -C/--context (e.g. -C5) - Increases context, so you see the surrounding code.

  • --color=auto - Mark up the matching text.

  • -H - Displays filename where the text is found.

  • -c - Displays count of matching lines. Can be combined with -H.

Solution 7 - Linux

List of file names containing a given text

First of all, I believe you have used -H instead of -l. Also you can try adding the text inside quotes followed by {} \.

find / -type f -exec grep -l "text-to-find-here" {} \; 


Let's say you are searching for files containing specific text "Apache License" inside your directory. It will display results somewhat similar to below (output will be different based on your directory content).

bash-4.1$ find . -type f -exec grep -l "Apache License" {} \; 

Remove case sensitiveness

Even if you are not use about the case like "text" vs "TEXT", you can use the -i switch to ignore case. You can read further details here.

Hope this helps you.

Solution 8 - Linux

If your grep doesn't support recursive search, you can combine find with xargs:

find / -type f | xargs grep 'text-to-find-here'

I find this easier to remember than the format for find -exec.

This will output the filename and the content of the matched line, e.g.


Optional flags you may want to add to grep:

  • -i - case insensitive search
  • -l - only output the filename where the match was found
  • -h - only output the line which matched (not the filename)

Solution 9 - Linux

grep -insr "pattern" *
  • i: Ignore case distinctions in both the PATTERN and the input files.
  • n: Prefix each line of output with the 1-based line number within its input file.
  • s: Suppress error messages about nonexistent or unreadable files.
  • r: Read all files under each directory, recursively.

Solution 10 - Linux

There's a new utility called The Silversearcher

sudo apt install silversearcher-ag

It works closely with Git and other VCS. So you won't get anything in a .git or another directory.

You can simply use

ag "Search query"

And it will do the task for you!

Solution 11 - Linux

> How do I find all files containing specific text on Linux? > (...) > > I came across this solution twice: > > find / -type f -exec grep -H 'text-to-find-here' {} \;

If using find like in your example, better add -s (--no-messages) to grep, and 2>/dev/null at the end of the command to avoid lots of Permission denied messages issued by grep and find:

find / -type f -exec grep -sH 'text-to-find-here' {} \; 2>/dev/null

find is the standard tool for searching files - combined with grep when looking for specific text - on Unix-like platforms. The find command is often combined with xargs, by the way.

Faster and easier tools exist for the same purpose - see below. Better try them, provided they're available on your platform, of course:

Faster and easier alternatives

RipGrep - fastest search tool around:

rg 'text-to-find-here' / -l

The Silver Searcher:

ag 'text-to-find-here' / -l


ack 'text-to-find-here' / -l

Note: You can add 2>/dev/null to these commands as well, to hide many error messages.

Warning: unless you really can't avoid it, don't search from '/' (the root directory) to avoid a long and inefficient search! So in the examples above, you'd better replace '/' by a sub-directory name, e.g. "/home" depending where you actually want to search...

Solution 12 - Linux


find . -name "*.txt" | xargs grep -i "text_pattern"

Solution 13 - Linux

grep -lrnw '/root/Desktop/ipozal' -e 'geolocation'

For example:

  • my folder name is "ipozal"
  • it placed on "/root/Desktop"
  • I want to find this text on all files in it "geolocation"

Solution 14 - Linux

Use pwd to search from any directory you are in, recursing downward

grep -rnw `pwd` -e "pattern"

Update Depending on the version of grep you are using, you can omit pwd. On newer versions . seems to be the default case for grep if no directory is given thus:

grep -rnw -e "pattern"


grep -rnw "pattern"

will do the same thing as above!

Solution 15 - Linux

This grep command will give you precise result when you are searching for specific text on linux -

grep -inRsH "Text to be searched" /path/to/dir (it can be '.')

  • i stands for ignore case distinctions

  • R stands for recursive and it also include symlinks. Better to use 'R' instead 'r'

  • n stands for "it will print line number".

  • s stands for "suppress error messages"

  • H stands for "it will print the file name for each match"

Solution 16 - Linux

grep can be used even if we're not looking for a string.

Simply running,

grep -RIl "" .

will print out the path to all text files, i.e. those containing only printable characters.

Solution 17 - Linux

If you strictly want to use find then use find + grep:

find /path/to/somewhere/ -type f -exec grep -nw 'textPattern' {} \;


  1. Use find to search files,
  2. Execute grep on all of them.

This gives you the power of find to find files.

  • Use -name Pattern if you want to grep only certain files:

find /path/to/somewhere/ -type f -name \*.cpp -exec grep -nw 'textPattern' {} \;

You can use different options of find to improve your file search.

Solution 18 - Linux

Silver Searcher is a terrific tool, but ripgrep may be even better.

It works on Linux, Mac and Windows, and was written up on Hacker News a couple of months ago (this has a link to Andrew Gallant's Blog which has a GitHub link):

Ripgrep – A new command line search tool

Solution 19 - Linux

Here are the several list of commands that can be used to search file.

grep "text string to search” directory-path

grep [option] "text string to search” directory-path

grep -r "text string to search” directory-path

grep -r -H "text string to search” directory-path

egrep -R "word-1|word-2” directory-path

egrep -w -R "word-1|word-2” directory-path

Solution 20 - Linux

I am fascinated by how simple grep makes it with 'rl':

grep -rl 'pattern_to_find' /path/where/to/find

-r to recursively find a file / directory inside directories..
-l to list files matching the 'pattern'

> Use '-r' without 'l' to see the file names followed by text in which the pattern is found!

grep -r 'pattern_to_find' /path/where/to/find

It works just perfect...

Solution 21 - Linux

find /path -type f -exec grep -l "string" {} \;

Explanation from comments

find is a command that lets you find files and other objects like directories and links in subdirectories of a given path. If you don't specify a mask that filesnames should meet, it enumerates all directory objects.

-type f specifies that it should proceed only files, not directories etc.
-exec grep specifies that for every found file, it should run grep command, passing its filename as an argument to it, by replacing {} with the filename

Solution 22 - Linux

Hope this is of assistance...

Expanding the grep a bit to give more information in the output, for example, to get the line number in the file where the text is can be done as follows:

find . -type f -name "*.*" -print0 | xargs --null grep --with-filename --line-number --no-messages --color --ignore-case "searthtext"

And if you have an idea what the file type is you can narrow your search down by specifying file type extensions to search for, in this case .pas OR .dfm files:

find . -type f \( -name "*.pas" -o -name "*.dfm" \) -print0 | xargs --null grep --with-filename --line-number --no-messages --color --ignore-case "searchtext"

Short explanation of the options:

  1. . in the find specifies from the current directory.
  2. -name "*.*" : for all files ( -name "*.pas" -o -name "*.dfm" ) : Only the *.pas OR *.dfm files, OR specified with -o
  3. -type f specifies that you are looking for files
  4. -print0 and --null on the other side of the | (pipe) are the crucial ones, passing the filename from the find to the grep embedded in the xargs, allowing for the passing of filenames WITH spaces in the filenames, allowing grep to treat the path and filename as one string, and not break it up on each space.

Solution 23 - Linux

If you are in a Git repository, you can use:

git grep something

Solution 24 - Linux

grep "text-to-find-here" file_name


grep "text-to-find-here" directory_path/*

If you want to search current directory:

grep "text-to-find-here" *

Solution 25 - Linux

A Simple find can work handy. alias it in your ~/.bashrc file:

alias ffind find / -type f | xargs grep

Start a new terminal and issue:

ffind 'text-to-find-here'

Solution 26 - Linux

grep is your good friend to achieve this.

grep -r <text_fo_find> <directory>

If you don't care about the case of the text to find, then use:

grep -ir <text_to_find> <directory>

Solution 27 - Linux

I wrote a Python script which does something similar. This is how one should use this script.

./ path pattern_to_search [file_pattern]

The first argument, path, is the directory in which we will search recursively. The second argument, pattern_to_search, is a regular expression which we want to search in a file. We use the regular expression format defined in the Python re library. In this script, the . also matches newline.

The third argument, file_pattern, is optional. This is another regular expression which works on a filename. Only those files which matches this regular expression will be considered.

For example, if I want to search Python files with the extension py containing Pool( followed by word Adaptor, I do the following,

./ . "Pool(.*?Adaptor"  .*py

And voila, it generates the path of matched files and line number at which the match was found. If more than one match was found, then each line number will be appended to the filename.

Solution 28 - Linux


find / -type f -exec grep -H 'text-to-find-here' {} \;

which will search all file systems, because / is the root folder.

For home folder use:

find ~/ -type f -exec grep -H 'text-to-find-here' {} \;

For current folder use:

find ./ -type f -exec grep -H 'text-to-find-here' {} \;

Solution 29 - Linux

There is an ack tool that would do exactly what you are looking for.

ack -i search_string folder_path/*

You may ignore -i for case sensitive search

Solution 30 - Linux

To search for the string and output just that line with the search string:

for i in $(find /path/of/target/directory -type f); do grep -i "the string to look for" "$i"; done


for i in $(find /usr/share/applications -type f); \
do grep -i "web browser" "$i"; done

To display filename containing the search string:

for i in $(find /path/of/target/directory -type f); do if grep -i "the string to look for" "$i" > /dev/null; then echo "$i"; fi; done;


for i in $(find /usr/share/applications -type f); \
do if grep -i "web browser" "$i" > /dev/null; then echo "$i"; \
fi; done;

Solution 31 - Linux

The below command will work fine for this approach:

find ./ -name "file_pattern_name"  -exec grep -r "pattern" {} \;

Solution 32 - Linux


grep -c Your_Pattern *

This will report how many copies of your pattern are there in each of the files in the current directory.

Solution 33 - Linux

All previous answers suggest grep and find. But there is another way: Use Midnight Commander

It is a free utility (30 years old, proven by time) which is visual without being GUI. It has tons of functions, and finding files is just one of them.

Solution 34 - Linux

You can use below command as you don't want file name but you want to search from all the files. Here are i am capturing "TEXT" form All the log files making sure that file name is not printed

grep -e TEXT *.log | cut -d' ' --complement -s -f1

grep with -e option is quite quick compared to other option as it is for PATTERN match

Solution 35 - Linux

I tried the grep command below. It helps searching contents within my repository at /etc/yum.repos.d.

grep -Ril -e 'texttoSearch' /etc/yum.repos.d

Solution 36 - Linux

Try this:

find . | xargs grep 'word' -sl

Solution 37 - Linux

Avoid the hassle and install ack-grep. It eliminates a lot of permission and quotation issues.

apt-get install ack-grep

Then go to the directory you want to search and run the command below

cd /
ack-grep "find my keyword"

Solution 38 - Linux

Try this:

find / -type f -name "*" -exec grep -il "String_to_search" {} \;


for i in /*;do grep -Ril "String_to_search" $i;done 2> /dev/null

Solution 39 - Linux


grep -Erni + "text you wanna search"

The command will search recursively in all files and directories of the current directory and print the result.

Note: if your grep output isn't colored, you can change it by using the grep='grep --color=always' alias in your shell source file.

Solution 40 - Linux

If you have a set of files that you will always be checking you can alias their paths, for example:

alias fd='find . -type f -regex ".*\.\(inc\|info\|module\|php\|test\|install\|uninstall\)"'

Then you can simply filter the list like this:

grep -U -l $'\015' $(fd)

Which filters out the list fd to files that contain the CR pattern.

I find that aliasing the files that I am interested in helps me create easier scripts then always trying to remember how to get all those files. The recursive stuff works as well but sooner or later you are going to have to contend with weeding out specific file types. Which is is why I just find all the file types I'm interested in to begin with.

Solution 41 - Linux

You can use the following commands to find particular text from a file:

cat file | grep 'abc' | cut -d':' -f2

Solution 42 - Linux

find with xargs is preferred when there are many potential matches to sift through. It runs more slowly than other options, but it always works. As some have discovered,xargs does not handle files with embedded spaces by default. You can overcome this by specifying the -d option.

Here is @RobEarl's answer, enhanced so it handles files with spaces:

find / -type f | xargs -d '\n' grep 'text-to-find-here'

Here is @venkat's answer, similarly enhanced:

find . -name "*.txt" | xargs -d '\n' grep -i "text_pattern"

Here is @Gert van Biljon's answer, similarly enhanced:

find . -type f -name "*.*" -print0 | xargs -d '\n' --null grep --with-filename --line-number --no-messages --color --ignore-case "searthtext"

Here is @LetalProgrammer's answer, similarly enhanced:

alias ffind find / -type f | xargs -d '\n' grep

Here is @Tayab Hussain's answer, similarly enhanced:

find . | xargs -d '\n' grep 'word' -sl

Solution 43 - Linux

Try this

find . -type f -name some_file_name.xml -exec grep -H PUT_YOUR_STRING_HERE {} \;

Solution 44 - Linux

As Peter in the previous answer mentioned, all previous answers suggest grep and find.

But there is a more sophisticated way using Gnome Commander with a perfect GUI and with tons of options since 2001, and finding files is just one of them. It is a free utility as well, proven by time.

Solution 45 - Linux

See also The Platinium Searcher, which is similar to The Silver Searcher and it's written in Go.


pt -e 'text to search'

Solution 46 - Linux

You can use ripgrep which will respect by the default project's .gitignore file.


To suppress Permission denied errors:

rg -i rustacean 2> /dev/null

Which will redirect the standard error (stderr) output to /dev/null.

Solution 47 - Linux

GUI Search Alternative - For Desktop Use:

- As the question is not precisely asking for commands

Searchmonkey: Advanced file search tool without having to index your system using regular expressions. Graphical equivalent to find/grep. Available for Linux (Gnome/KDE/Java) and Windows (Java) - open source GPL v3


  • Advanced Regular Expressions
  • Results shown in-context
  • Search containing text
  • Panel to display line containing text
  • New 2018 updates
  • etc.

Download - Links:



Enter image description here

Solution 48 - Linux

> I'm trying to find a way to scan my entire Linux system for all files containing a specific string of text. ... Is this close to the proper way to do it? If not, how should I? ... This ability to find text strings in files would be extraordinarily useful for some programming projects I'm doing.

While you should never replace (or alias) a system command with a different program, due to risk of mysterious breakage of scripts or other utilities, if you are running a text search manually or from your own scripts or programs you should consider the fastest suitable program when searching a large number of files a number of times. Ten minutes to half an hour time spent installing and familiarizing yourself with a better utility can be recovered after a few uses for the use-case you described.

A webpage offering a "Feature comparison of ack, ag, git-grep, GNU grep and ripgrep" can assist you to decide which program offers the features you need.

  • Andrew Gallant's Blog claims: "ripgrep is faster than {grep, ag, git grep, ucg, pt, sift}" (a claim shared by some of the others, this is why a feature comparison is helpful). Of particular interest is his section on regex implementations and pitfalls.

    The following command searches all files, including hidden and executable:

    $ rg -uuu foobar

  • The Silver Searcher (ag) claims it is 5-10x faster than Ack. This program is suggested in some other answers. The GitHub doesn't appear as recent as ripgrep's and there are noticably more commits and branches with fewer releases, it's hard to draw an absolute claim based on those stats. The short version: ripgrep is faster, but there's a tiny learning curve to not get caught by the differences.

  • So what could be next, you guessed it, the platinum searcher. The claims are: it searches code about 3–5× faster than ack, but its speed is equal to the silver searcher. It's written in GoLang and searches UTF-8, EUC-JP and Shift_JIS files; if that's of greater interest. The GitHub is neither particularly recent or active. GoLang itself has a fast and robust regex, but the platinum searcher would be better recommended if it had a better user interest.

For a combination of speed and power indexed query languages such as ElasticSearch or Solr can be a long term investment that pays off, but not if you want a quick and simple replacement for grep. OTOH both have an API which can be called from any program you write, adding powerful searches to your program.

While it's possible to spawn an external program, execute a search, intercept its output and process it, calling an API is the way to go for power and performance.

>This question was protected Aug 6 '15 at 19:34 with this caution:
>   We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations.

While some answers suggest alternative ways to accomplish a search they don't explain why other than it's "free", "faster", "more sophisticated", "tons of features", etc. Don't try to sell it, just tell us "why your answer is right". I've attempted to teach how to choose what's best for the user, and why. This is why I offer yet another answer, when there are already so many. Otherwise I'd agree that there are already quite a few answers; I hope I've brought a lot new to the table.

Solution 49 - Linux

My use case was to find Python code I had written way back that wrote jsonlines a particular way. I knew that jsonl would be part of the function name and to_json would appear in the body, but not much else.

Despite 50 answers, finding more than one string in the same file (whether or not in the same line) hasn't been answered.

The -q in grep is for quiet. Nothing is printed, only the return value is set. Thus the -print at the end. Each -exec only runs if the previous one succeeded. So if you have many files it pays to think about patterns that will eliminate files you aren't interested in.

find . -type f -name "*.py" \
  -exec grep -q -e 'to_json' {} \; \
  -exec grep -q -e 'def\s.*jsonl' {} \; \

Solution 50 - Linux

Your command is correct. You just need to add -l to grep:

find / -type f -exec grep -l 'text-to-find-here' {} \;

Solution 51 - Linux

Kindly customize the below command according to demand and find any string recursively from files.

grep -i hack $(find /etc/ -type f)

Solution 52 - Linux

Try this command. Which will give you the files containing the pattern you entered.

sudo grep -inr "your-pattern" /

Here: i - Ignore case distinctions, so that characters that differ only in case match each other.

n - Make sure that the first character of actual line content lies on a tab stop, so that the alignment of tabs looks normal.

r - Read all files under each directory, recursively, following symbolic links only if they are on the command line. Note that if no file operand is given, grep searches the working directory.

Solution 53 - Linux

You can also use awk:

awk '/^(pattern)/{print}' /path/to/find/*

pattern is the string you want to match in the files.

Solution 54 - Linux

Find any files whose name is ".kube/config", and content include eks_use1d:

locate ".kube/config" | xargs -i sh -c 'echo \\n{};cat {} | grep eks_use1d'


All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionNathanView Question on Stackoverflow
Solution 1 - Linuxrakib_View Answer on Stackoverflow
Solution 2 - LinuxfedorquiView Answer on Stackoverflow
Solution 3 - LinuxStephanView Answer on Stackoverflow
Solution 4 - Linuxlearner_19View Answer on Stackoverflow
Solution 5 - LinuxA RView Answer on Stackoverflow
Solution 6 - LinuxkenorbView Answer on Stackoverflow
Solution 7 - LinuxlkamalView Answer on Stackoverflow
Solution 8 - LinuxRobEarlView Answer on Stackoverflow
Solution 9 - LinuxenfinetView Answer on Stackoverflow
Solution 10 - LinuxNeil AgarwalView Answer on Stackoverflow
Solution 11 - LinuxBludzeeView Answer on Stackoverflow
Solution 12 - LinuxvenkatView Answer on Stackoverflow
Solution 13 - LinuxEyni KaveView Answer on Stackoverflow
Solution 14 - LinuxmahatmanichView Answer on Stackoverflow
Solution 15 - Linuxshashank aroraView Answer on Stackoverflow
Solution 16 - LinuxAlex JasminView Answer on Stackoverflow
Solution 17 - LinuxBreakBadSPView Answer on Stackoverflow
Solution 18 - LinuxAAAfarmclubView Answer on Stackoverflow
Solution 19 - LinuxAtul ArvindView Answer on Stackoverflow
Solution 20 - Linuxnitinr708View Answer on Stackoverflow
Solution 21 - LinuxVinod JoshiView Answer on Stackoverflow
Solution 22 - LinuxGert van BiljonView Answer on Stackoverflow
Solution 23 - LinuxDorianView Answer on Stackoverflow
Solution 24 - LinuxMichaelView Answer on Stackoverflow
Solution 25 - LinuxdanglingpointerView Answer on Stackoverflow
Solution 26 - LinuxPrashView Answer on Stackoverflow
Solution 27 - LinuxDilawarView Answer on Stackoverflow
Solution 28 - Linuxuser4863663View Answer on Stackoverflow
Solution 29 - LinuxPalView Answer on Stackoverflow
Solution 30 - Linuxuser3124504View Answer on Stackoverflow
Solution 31 - LinuxPradeep GoswamiView Answer on Stackoverflow
Solution 32 - LinuxDr_HopeView Answer on Stackoverflow
Solution 33 - LinuxPeter M. - stands for MonicaView Answer on Stackoverflow
Solution 34 - LinuxMitul PatelView Answer on Stackoverflow
Solution 35 - Linuxmuhammad tayyabView Answer on Stackoverflow
Solution 36 - LinuxTayab HussainView Answer on Stackoverflow
Solution 37 - LinuxKareemView Answer on Stackoverflow
Solution 38 - LinuxVIPIN KUMARView Answer on Stackoverflow
Solution 39 - LinuxbaldashView Answer on Stackoverflow
Solution 40 - LinuxdkinzerView Answer on Stackoverflow
Solution 41 - LinuxiamjaypView Answer on Stackoverflow
Solution 42 - LinuxMike SlinnView Answer on Stackoverflow
Solution 43 - LinuxSireesh YarlagaddaView Answer on Stackoverflow
Solution 44 - LinuxGeeocodeView Answer on Stackoverflow
Solution 45 - LinuxGustavo PauloView Answer on Stackoverflow
Solution 46 - LinuxLevonView Answer on Stackoverflow
Solution 47 - LinuxintikaView Answer on Stackoverflow
Solution 48 - LinuxRobView Answer on Stackoverflow
Solution 49 - LinuxLeoView Answer on Stackoverflow
Solution 50 - LinuxFariZView Answer on Stackoverflow
Solution 51 - Linuxlinux.cnfView Answer on Stackoverflow
Solution 52 - Linuxchaitanya sonagaraView Answer on Stackoverflow
Solution 53 - LinuxKathan TripathiView Answer on Stackoverflow
Solution 54 - LinuxJohn ZhengView Answer on Stackoverflow