My understanding is that command starts some background process that perhaps will write some output to the terminal later. If command terminates before that the ssh session will be terminated and there will be no terminal for the background program to write to One simple and naive solution is to just sleep long enough ssh user@ip "command; sleep 30m" >> /myfile A better solution than sleep would be to wait for the background process(es) to finish in some more intelligent way, but that is impossible to say without further details.
My understanding is that command starts some background process that perhaps will write some output to the terminal later. If command terminates before that the ssh session will be terminated and there will be no terminal for the background program to write to. One simple and naive solution is to just sleep long enough ssh user@ip "command; sleep 30m" >> /myfile A better solution than sleep would be to wait for the background process(es) to finish in some more intelligent way, but that is impossible to say without further details.
Thanks a lot. But the remote system is a closed system with no access to a real shell (think of a cisco ssh shell), so no custom commands are allowed. To simplify what I need is I want to have the following command executed without closing the ssh channel once the execution finished (this must be done without chaning anything at the "command" itself, so no remote changing): ssh user@ip "command" – sven Jan 28 '10 at 15:03.
Something more powerful than bash would be Python with Paramiko and PyExpect.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.