-bash: rails: command not found

[Matt]

I know lots of people seem to have this problem...I've been through the
posts and have followed the advice, but I'm still having trouble.

Terminal isn't recognizing the rails command.

When I do a locate on rails, then echo $PATH, I'm told,

/bin:/sbin:/usr/bin:/usr/sbin

However, when I go through these directories in Terminal, rails is not
there. Instead, it's in usr/local/bin. My bash_login file reads

export PATH="/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:$PATH"

Why is echo $PATH telling me that rails is in a different directory
than it actually is? And how can I get terminal to recognize the
command?


thanks,
matt

 

[Ben Bleything]

To find out where rails really is, say:

find /usr -name "rails"

Of course, this is going to take forever. If locate tells you a
location, try that. If rails isn't there, run sudo updatedb and try
again.

It's pretty much only ever going to end up in a handful of places
(unless you're on a really weird platform). /usr/bin, /usr/local/bin,
/opt/local/bin (mac with dports)...

If you have to use find, pass in -type f:

find /usr -type f -name rails

Which'll only find files, and run quicker than without.


Ben

 

[matt neuburg]

Of course, this is going to take forever.

find /usr -name "dummy"

takes four seconds on my machine. We're looking for an exact match and
there just ain't that much stuff in /usr. m.

 

[Ben Bleything]

find /usr -name "dummy"

takes four seconds on my machine. We're looking for an exact match and
there just ain't that much stuff in /usr. m.

Significantly longer on mine, but I've got a slow HD and my /usr/local
is packed full of stuff.

The point is, always better to use everything you can to focus your
search.

Ben

 

[Matt]

Figured it out. Everything was set up right, but my bash_login file
should have been named .bash_login. Newbie mistake.