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.
I'm currently using PuTTY to connect to my Slack 9.1 box via my laptop (same LAN). I'm wondering if there's any way I can run a program (say, SETI@Home or whatnot) and not have to have PuTTY maintain a connection; ie I can log in at a later time (remotely) and either check up on the status of the program or end it or whatnot.
Look up the man or info page for nohup. This command will run a program in the background, put stderr streams into a file (nohup.out) and allow you to logout. nohup stand for no HUP.
Okay, I've started my process with nohup (requiring root), and logged out. Logged back in and I can't find the process to kill (making sure I could, should I want the process killed). "fg" doesn't work (tells me there's nothing in the background), and the output of "ps -aux" is pretty standard, with no mention of the program I started.
You will need to su to root after logging in again. Then if you ps aux | grep <program name> you should be able to find it. Maybe the process aborted at some point before you logged back in.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.