Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
well just quit the script, and the shell will collapse back until ssh itself is terminated. if you just run an "ls" you'll see ssh quits after the ls. same goes for any other script you wish to execute.
what i want to do, though, is to start a script on the remote and
close the ssh connection, leaving the remote script running. is
this not possible? the remote script will take a long time to run
and i want to move on to other parts of the local script which
initiated the remote one. if i leave the ssh connection up and
try to move on in the local script, the console screen keeps
getting interrupted with output from the remote. that's one reason
i just want to start the remote and leave. any thoughts on how to
do this? is it even possible? might i have to open new consoles for
each new connection?
1. ssh into the remote
2. start the 'commands.sh' script as a background script
3. return to the local script or shell (because of the '&')
leaving the 'commands.sh' script running remotely?
do i have that right?
thanks so much. nohup sounds very useful. (assuming i'm
getting it)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.