ssh question

On Fri, 14 Jul 2006 17:14:12 GMT, Cardiff IT Support Ltd staggered into the Black Sun and said:

You can't, at least not easily. If you'd started your initial session with screen, you could detach (or force-detach) your screen session, then log in again from elsewhere, start screen, and reattach it. screen is a very useful and nifty program if you work on terminals a lot; checkusr-share-doc-screen* for guides and tutorials. If that directory doesn't exist, "apt-get install screen" or "emerge screen" or do whatever your distro does for installing screen.

If you started a long process that output to stdout and-or stderr, you could've redirected those things to a file, and then you could check up on what's going on by using tail -f on the file.

If the process was running on a tty (not a pty), you could catdev-vcsN , and see what's currently on that tty.

But if you did none of those things, you have few options. There may be some sort of way to get at stdout, but the obvious way of looking inproc-$PID-fddoesn't cut it. Trying to catdev-pts-N doesn't work either. I've seen this question asked a few times, and I can't recall anyone ever coming up with a better solution than "use screen". HTH anyway,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL