> [snip] > that is because Mac OSX is missing a package-managment and so you need > a little knowledge about your OS to fix the PATH or you have to use > full-qualified calls or configure/install your software to locations > which are already in the path > > "which mysqldump" as normal user wil tell you where it is really > [harry@srv-rhsoft:~]$ which mysqldump > /usr/bin/mysqldump
Thank you Richard, Andy, and Reindl ! Of course you all nailed it. Reindl, I especially appreciate you addressing each point, as it pointed me in the right direction to fill in the understanding-holes on all those topics! Some things I (partially) knew, but did not remember today because I don't have to deal in these areas much. For right now, I just used full paths both for the command and for the output. Just a side note, that: Govind% which mysqldump mysqldump: Command not found. Govind% which /usr/local/mysql/bin/mysqldump /usr/local/mysql/bin/mysqldump kind of defeats the purpose of having to know the path in advance in order to use the command to detect the path ;-) -Govinda -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
