Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You question is a little vague. What information do you want from the process? If you just want things like memory usage or processor usage, you can use "ps" or "top" after you ssh back in. If you want control over the process as if you had executed it from the command line after you ssh back in, you can use something like "screen".
Which process & where you're doing ssh... please specify.
Meanwhile, a process can be identified by it's process ID i.e. PID. And you can check processes using ps command. To check processes of a user username, invoke:-
If what you are asking for is a way to see what that process is writing to the console where it was started, then the answer is "no" unless the terminal emulator for that console provides some hook to let you see what is displayed. If what you want is a way to look into the internal workings of that process, then yes, you can tell gdb or strace to attach to that running process and both view and control it, but gdb in particular isn't likely to be of much use unless you've got the source code in hand and the program was compiled with debugging symbols included.
You might pipe the output through tee and write a copy to a file you could examine. Just watch out for output buffering. By default, output going to a terminal is line-buffered (flushed after each newline), but sending the output through a pipe would make the default block-buffered (typically 4KB blocks), so the output would be delayed until a block is filled. The program doing the computation would need a way to select how output is buffered, or you might take a look at the unbuffer utility (part of the expect package).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.