99

What's the difference between which and whereis ?

migrated from stackoverflow.com Sep 12 '09 at 22:41

This question came from our site for professional and enthusiast programmers.

  • I'm sorry but on my 10.5.8 OS X system which and whereis always give the same results. Maybe this is a very OS X specific question, since I agree, a different result is expected. Maybe whereis does not comply to what it should do. At least the two examples (see below) are not working: whereis ls and whereis php always give the same result as which ... Can anybody confirm this? Does Snow Leopard behave the same? – Wolf Sep 12 '09 at 23:11
  • Yeah I know, thats why I asked this question. – mk12 Sep 12 '09 at 23:25
  • @Wolf here's an example of which and whereis giving different output (on macOS Sierra) apple.stackexchange.com/questions/259047/… – Matthew Oct 28 '16 at 10:09
  • @mk12 I feel like type is superior. It also knows about defined aliases, functions etc – Blauhirn Aug 19 '18 at 3:32
112

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
  • 29
    didn't know about whatis, thanks. – mk12 Sep 12 '09 at 20:39
  • 1
    BTW, I'd remove the "osx" tag, as this question applies to all unix variants (including Linux, BSD, Mac OS X, ...) – Denilson Sá Maia Sep 12 '09 at 20:44
  • changed to unix – mk12 Sep 12 '09 at 23:24
  • 1
    There's more to it than that. On my system, whereis and which return different executable paths. I can only get the path to the one that actually runs with whereis, not the one for which. – Jordan Reiter Aug 21 '16 at 22:25
  • 1
    @JordanReiter: It can't be! which shows the actual path. Are you sure the path pointed by which isn't just a symlink to the path pointed by whereis? Maybe it is a shell alias. In bash, try running type your_cmd_here. – Denilson Sá Maia Aug 22 '16 at 0:01
21

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)

  • What is *nix? – mk12 Sep 12 '09 at 20:19
  • 2
    Unix, Linux etc. (Mac OS X belonging in the etc.) – Tom Sep 12 '09 at 20:23
  • 8
    Ohhh, haha, I always thought that stack overflow was censoring the U in unix whenever I saw that for some reason.. – mk12 Sep 12 '09 at 22:19
  • Nope. Just a fairly common convention of creative wildcard use to refer to a family of similar operating systems. ;) – Dav Sep 12 '09 at 22:28
6

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.

1

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? :)

  • did you run updatedb command? locate relies on that as far as I remember – Oliver M Grech Feb 2 '18 at 10:37

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.