UNIX/BSD people
01-09-2004, 10:50 AM
#1
still alive
Thread Starter
Join Date: Sep 2002
Location: Huntsville, AL
Posts: 841
Likes: 0
Received 0 Likes
on
0 Posts
UNIX/BSD people
I'm logged into my server remotely through ssh and I initiate a port install. If I close ssh while it is compiling, will the server keep compiling? I don't wanna screw something up, but I can't stay logged in forever.
01-09-2004, 10:53 AM
#3
still alive
Thread Starter
Join Date: Sep 2002
Location: Huntsville, AL
Posts: 841
Likes: 0
Received 0 Likes
on
0 Posts
Originally posted by antarius
Depends.
It's screwed up before on me like that, and didn't another time.
I'd say run a screen, then compile, then detach, then close SSH.
Depends.
It's screwed up before on me like that, and didn't another time.
I'd say run a screen, then compile, then detach, then close SSH.
Can I ^c and pause it?
01-09-2004, 10:55 AM
#4
Large Member
Join Date: Oct 2000
Location: Bay Area, CA
Posts: 4,735
Likes: 0
Received 0 Likes
on
0 Posts
So quit the compiling, to be safe.
Then re-log in, type "screen", then go compile your shit, then hit ctrl+d while it's compiling, and close telnet.
Next time you log in just type screen -r and resume where you left off (it will continue compiling while detached)
Then re-log in, type "screen", then go compile your shit, then hit ctrl+d while it's compiling, and close telnet.
Next time you log in just type screen -r and resume where you left off (it will continue compiling while detached)
01-09-2004, 10:59 AM
#6
Large Member
Join Date: Oct 2000
Location: Bay Area, CA
Posts: 4,735
Likes: 0
Received 0 Likes
on
0 Posts
Okay... let me explain.
Telnet to your machine.
Type "screen"
That starts a process under a "screen", you can then detach from this "screen" but your machine doesn't realize you've disconnected, and keeps doing whatever it is you were doing under that "screen".
So, run "screen", then start your business (compiling whatever it is)
Then type ctrl+d, that will detach you from screen and put you back into your normal console - all the while your compiling will still be going on behind that "screen".
Ctrl+x to quit or just exit telnet, doesnt matter.
Next time you log in, type screen-r to resume that particular screen and see if your compiling finished. ctrl+X or ctrl+c a hundred million times, to kill the screen (screen -wipe also does it)
I use it when I'm on IRC from somewhere like work. I have to close the window but I don't want to exit IRC. So I "screen", then run BX, then just detach and exit my Telnet screen when the boss would come around. Come back, telnet/login, "screen -r" and continue reading where I left off.
Telnet to your machine.
Type "screen"
That starts a process under a "screen", you can then detach from this "screen" but your machine doesn't realize you've disconnected, and keeps doing whatever it is you were doing under that "screen".
So, run "screen", then start your business (compiling whatever it is)
Then type ctrl+d, that will detach you from screen and put you back into your normal console - all the while your compiling will still be going on behind that "screen".
Ctrl+x to quit or just exit telnet, doesnt matter.
Next time you log in, type screen-r to resume that particular screen and see if your compiling finished. ctrl+X or ctrl+c a hundred million times, to kill the screen (screen -wipe also does it)
I use it when I'm on IRC from somewhere like work. I have to close the window but I don't want to exit IRC. So I "screen", then run BX, then just detach and exit my Telnet screen when the boss would come around. Come back, telnet/login, "screen -r" and continue reading where I left off.