Timeline for Best way to connect to an existing user context through SSH
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2015 at 18:45 | comment | added | Viktor Benei | @EricRenouf sorry, I was referring to collecting the outputs (stdout) of the command. I also added an edit to the end of the question that we need to get the exit code of the command as well, in addition to the outputs. | |
| Apr 15, 2015 at 18:45 | comment | added | LhasaDad | I'll also point at STAF (staf.sourceforge.net) as an option for managed remote command execution. I have used it for things like what your trying to do. just a thought. | |
| Apr 15, 2015 at 18:38 | comment | added | Eric Renouf | When you're talking about collecting logs, do you mean getting the output of stdout? If so I think lhasadad was probably on the right track. If you have the commands teeing their output, you could have another ssh session that is watching that file in "real time." If it's writing to a real log file you could have an ssh session tail-ing that file the whole time. If those won't work I'll need a bit more info about why they aren't meeting the need in order to help find a better answer | |
| Apr 15, 2015 at 16:27 | comment | added | Viktor Benei | @lhasadad We would preferably collect the logs through the caller process and also collect the command's exit code there because both have to be transferred to a server. Do you know an example we could use? | |
| Apr 15, 2015 at 16:19 | comment | added | LhasaDad | how about tee-ing the output of the commands to a file so that you can see on the screen and later collect from the session? | |
| Apr 15, 2015 at 15:53 | comment | added | Viktor Benei | We tried but could not figure out a way to collect the logs in a similar way we do with SSH. Could you show an example call which works similarly in terms of log output? | |
| Apr 15, 2015 at 15:49 | history | answered | Eric Renouf | CC BY-SA 3.0 |