bryn wrote:
Sorry if you didn't get what I meant.
The [2]+ Stopped occurs as a side effect of issuing ls - no kb interrupts sent.
No! the first ls has completed, thus the job has finished, thus it has stopped.
It hadn't completed, I was just pointing out that (completed|finished)!=stopped.
try:
$(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
-- [EMAIL PROTECTED] mailing list
