Why is it sometimes that which and whereis fail to find a command?
e.g.
$ awswl
-bash: /Users/geoffrey/Library/Python/2.7/bin/awswl: No such file or directory
$ which awswl
$ whereis awswl
$
I installed awswl with pip, and there seems to be a bug with the Python2 support, so I uninstalled it with pip and reinstalled with pip3. Having done so, when I run awswl I get this error:
$ awswl
-bash: /Users/geoffrey/Library/Python/2.7/bin/awswl: No such file or directory
This isn't just command not found, something is clearly found, seems plausibly a symlink or some other script that would link to awswl. But neither which nor whereis is doing a good job of telling me where the thing that is left behind is. Why?
type -a awswlsay? possibly your shell has hashed the old location – steeldriver Apr 14 '18 at 15:19$ type -a awswlresults in-bash: type: awswl: not found– Geoffrey Wiseman Apr 14 '18 at 15:47hash -rseems to have caused the awswl error to go 'way. – Geoffrey Wiseman Apr 14 '18 at 15:49