which/whereis differences
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Digital Sunset Looping
--
Chapters
00:00 Which/Whereis Differences
00:11 Answer 1 Score 29
00:30 Answer 2 Score 7
01:07 Accepted Answer Score 178
01:41 Answer 4 Score 2
02:40 Thank you
--
Full question
https://superuser.com/questions/40301/wh...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#unix #terminal #path #which
#avk47
ACCEPTED ANSWER
Score 178
How about learning about whereis
and which
using whatis
?
$ whatis which
which (1) - shows the full path of (shell) commands
$ whatis whereis
whereis (1) - locate the binary, source, and manual page files for a command
Basically, whereis
searches for "possibly useful" files, while which
only searches for executables.
I rarely use whereis
. On the other hand, which
is very useful, specially in scripts. which
is the answer for the following question: Where does this command come from?
$ which ls
/bin/ls
$ whereis ls
ls: /bin/ls /usr/share/man/man1p/ls.1p.bz2 /usr/share/man/man1/ls.1.bz2
ANSWER 2
Score 29
whereis
searches the standard *nix locations for a specified command.
which
searches your user-specific PATH (which may include some of the locations whereis searches, and may not include others - it might also include some places that whereis
doesn't search if you'd added to your PATH)
ANSWER 3
Score 7
Quoting their man pages :
whereis :
whereis locates source/binary and manuals sections for specified files.
For instance :
$ whereis php
php: /usr/bin/php /usr/share/php /usr/share/man/man1/php.1.gz
ie, the "php" executable, and some other stuff (like man pages).
and which :
which returns the pathnames of the files which would be executed in the current environment
For instance :
$ which php
/usr/bin/php
ie, only the "php" executable.
ANSWER 4
Score 2
which search for executables in the directories specified by the environment variable PATH. And if found out, the full pathname of this executable will be printed.
$ which ls
/bin/ls
$ which ifconfig
$ # No output, because ifconfig only exist in root's PATH.
whereis search for executables, source files, and manual pages using a database built by system automatically.
$ whereis less
less: /bin/less /usr/bin/less /usr/bin/X11/less /usr/share/man/man1/less.1.gz
But it seems that whereis and locate don't use the same database. When I installed a software and then used whereis and locate immediately to search for this software. The result is that whereis could find out some files related to this software while locate couldn't. Do they really use different database? How the database work? --Well, how about refuse to be a pedant? :)