Ramey, ITS, CWRU[EMAIL PROTECTED]
http://cnswww.cns.cwru.edu/~chet/
--
View this message in context:
http://www.nabble.com/command-not-found-on-remote-server-tp20953229p20956977.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
Dolphin06 [EMAIL PROTECTED] wrote:
Can i do something like this :
ssh [EMAIL PROTECTED] export PATH=$PATH:/other path/ ; script param
You'd have to quote the sequence of commands that should run on the
remote host, so that the local bash and ssh see it as all one parameter:
ssh [EMAIL
Bob Proulx b...@proulx.com wrote:
Also, using full paths is frowned upon.
You mean invoking /directory/some-command directly instead of
PATH=$PATH:/directory
some-command
? It depends on the situation. If you think some-command is in
/directory, but you want to allow for the possibility that
Paul Jarc wrote:
Bob Proulx wrote:
Also, using full paths is frowned upon.
You mean invoking /directory/some-command directly instead of
PATH=$PATH:/directory
some-command
?
Yes. That is what I am saying.
It depends on the situation.
I can't disagree with that.
If you think
On Thu, Dec 11, 2008 at 03:35:33PM -0700, Bob Proulx wrote:
Paul Jarc wrote:
Bob Proulx wrote:
Also, using full paths is frowned upon.
You mean invoking /directory/some-command directly instead of
PATH=$PATH:/directory
some-command
?
...
... I was actually commenting on a
