Timeline for getting "No such file or directory" for a nonexistent command
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 31, 2013 at 1:56 | history | migrated | from stackoverflow.com (revisions) | ||
| Jul 30, 2013 at 21:20 | comment | added | Hristo Iliev |
It could also be hashing issue in the current bash session. In this case issuing the hash -r command or starting a new shell would solve the problem.
|
|
| Jul 30, 2013 at 17:30 | history | answered | LostAvatar | CC BY-SA 3.0 |