Neither "which" nor "find" commands work

hi there, could use some basic PATH advice, i think, or something

find sometimes work, but which hasn't ever seemed to. for years!

what am i doing wrong that the commands which and find rarely work?

they used to work on the workstations i used ages ago...

running 10.5.8 because i survive off of scientific shareware

am concerned that this is a symptom of a deeper ill

hopefully just my ignorance & nothing more :wink:

linkslice:~ Bryan$ echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
linkslice:~ Bryan$ which which
/usr/bin/which
linkslice:~ Bryan$ find /usr/bin -name which
/usr/bin/which

Thanks, that's helpful.

Looks like Fink is a bit pushy, it horned in and took over my which. Same diff I guess

keen:~ kicks$ echo $PATH
/usr/local/bin:/sw/bin:/sw/sbin:/Library/Frameworks/Python.framework/Versions/3.0/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/X11R6/bin
keen:~ kicks$ which which
/sw/bin/which
keen:~ kicks$ find /usr/bin -name which
/usr/bin/which

I know once ports (similar to fink) is installed, any gnu commands or bsd stuff I download takes precedence over what was there before, most likely because of edits that the program made in your .profile

Correct. It adds /sw/bin and /sw/sbin to the beginning of the path. If there's more than one of the same command the one it finds first is the one it will use. Since which exists in /sw and is before the /usr/bin in the path that is the one you want. If you want to chnge this behavior, edit your PATH and move those to later in the line.