bryn wrote:MAL wrotetry:
$(ssh [EMAIL PROTECTED] command) &
Sorry, no I don't get what you mean. What has running ssh inside a bash command substitution have to do with the problem I was asking about? It behaves oddly because it gets run in a sub-shell.
When I say this 'happens as a side effect of issuing ls', like I said, that was an example. It indicated the point in the process when it happened, I wasn't trying to say that that's the cause of the problem.
I've also just checked and the problem is independent of the shell - csh shows the same behaviour.
Anyway, this is all kinda academic as I just tried ssh'ing an account which needs a password while using the -f switch. According to the man page this won't work but it appears to go just fine.
Problem Solved.
Bryn
I assume it's due to a lack of a shell that is expected somewhere, thus forcing it to run a subshell, (on the server), works.
Figured I'd speak up about now.
There isnt a problem running ssh without a shell.
I run ssh for various uses: port forwarding, remote shells, and occasionally X forwarding. For simple port forwarding i use "ssh -
fN" (-f forks to background, -N means no shell (really: no command)). For X forwarding I usually ssh'd to 'host', and ran "program &" in it's shell as I often needed more than one program.
I never bothered redirecting output.
Try doing this instead:
[EMAIL PROTECTED]: ssh hex [EMAIL PROTECTED]: /usr/local/mozilla/mozilla &
if that works, step it up. You said keeping it in the forground didn't stop the process, so we can skip that step.
[EMAIL PROTECTED]: ssh -f hex /usr/local/mozilla/mozilla
At least this way, if ssh needed any information, it could still ask you on the console.
-Chris I
A kiss is a course of procedure, cunningly devised, for the mutual stoppage of speech at a moment when words are superfluous.
pgp00000.pgp
Description: PGP signature
