Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
I know that's the purpose of the screen command, but just to spread know-how, is that possible?
Example: 3441 pts/0 S+ 0:00 nano /etc/httpd/conf/httpd.conf
I remotely connect to a machine via ssh and started to edit apache conf and i did not used screen (me bad). The session timed out due to an internet glitch and I got disconnected. How can I reattach (speaking in screen terms) to that ssh session or gain control to the nano process (or any other)?
Thanks,
On Sep 20, 2006, at 10:41 AM, Erick Perez wrote:
Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
I know that's the purpose of the screen command, but just to spread know-how, is that possible?
Example: 3441 pts/0 S+ 0:00 nano /etc/httpd/conf/httpd.conf
I remotely connect to a machine via ssh and started to edit apache conf and i did not used screen (me bad). The session timed out due to an internet glitch and I got disconnected. How can I reattach (speaking in screen terms) to that ssh session or gain control to the nano process (or any other)?
if you didn't start an instance of screen to begin with, you're out of luck; screen can't help you reattach to any arbitrary process, only to other instances of screen.
does nano have a robust autosave/autorecover facility? if it does, just kill the nano process and start another (perhaps this time from within screen). if not, curse your bad luck and consider using vi next time, which can deal with this sort of problem.
-steve
-- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
On Wed, 2006-09-20 at 09:41 -0500, Erick Perez wrote:
Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
I know that's the purpose of the screen command, but just to spread know-how, is that possible?
Example: 3441 pts/0 S+ 0:00 nano /etc/httpd/conf/httpd.conf
I remotely connect to a machine via ssh and started to edit apache conf and i did not used screen (me bad). The session timed out due to an internet glitch and I got disconnected. How can I reattach (speaking in screen terms) to that ssh session or gain control to the nano process (or any other)?
You can't reconnect to a broken ssh connection, and in fact it should have killed all the processes you were running. However, some editors will save your work when terminated abnormally and let you recover in a different session. For example, if you used vi filename and were disconnected, you could recover later with vi -r filename I don't know anything about nano, though.
:( I will have to start all over again, hehehe. I will make sure to start screen next time. and I dont use vi, I use nano because to be honest with you it is easier for me to work with and is available in all redhat/centos versions. (maybe i should learn vi anyhow ;))
Thanks to Steve and Les,
On 9/20/06, Les Mikesell lesmikesell@gmail.com wrote:
On Wed, 2006-09-20 at 09:41 -0500, Erick Perez wrote:
Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
I know that's the purpose of the screen command, but just to spread know-how, is that possible?
Example: 3441 pts/0 S+ 0:00 nano /etc/httpd/conf/httpd.conf
I remotely connect to a machine via ssh and started to edit apache conf and i did not used screen (me bad). The session timed out due to an internet glitch and I got disconnected. How can I reattach (speaking in screen terms) to that ssh session or gain control to the nano process (or any other)?
You can't reconnect to a broken ssh connection, and in fact it should have killed all the processes you were running. However, some editors will save your work when terminated abnormally and let you recover in a different session. For example, if you used vi filename and were disconnected, you could recover later with vi -r filename I don't know anything about nano, though.
-- Les Mikesell lesmikesell@gmail.com
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Erick Perez wrote:
(maybe i should learn vi anyhow ;))
vi is not that hard to learn, and it is good to know for at least two reasons: it is in all unix variants and some recovery modes will only give you vi by default.
So the basic vi commands, hjkl c-f c-b G x i a o dd p and :x!, :q! is nice to know. Oh, and know that if a command does not work, just press Esc one more time :)
Erick Perez spake the following on 9/20/2006 8:29 AM:
:( I will have to start all over again, hehehe. I will make sure to start screen next time. and I dont use vi, I use nano because to be honest with you it is easier for me to work with and is available in all redhat/centos versions. (maybe i should learn vi anyhow ;))
So is vi. Just install vim and any vim options you want. I have used it since RedHat 6.
On Wednesday 20 September 2006 11:12, Les Mikesell wrote:
On Wed, 2006-09-20 at 09:41 -0500, Erick Perez wrote:
Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
You can't reconnect to a broken ssh connection, and in fact it should have killed all the processes you were running.
Unfortunately, I have seen many instances where ssh sessions do like this; if one happens to be running a yum update in one, and yum is downloading packages (putting yum into its unkillable mode, which, in my opinion is such an annoying thing; there have been a number of times I'd start up an update, have it run for a while, then need to leave (taking my laptop with me, and thus disconnecting the session, which can cause its own problems) where I'd like to just simply CTRL-C yum and have it do the Right Thing; yum just cycles to the next mirror (at least the last time a couple of weeks ago it did this) when you hit CTRL-C OR when you send yum a SIGTERM)), then you can get some really wierd artifacts with unkillable but not running yum processes; I have seen a few where SIGKILL didn't do anything, and all because of a network glitch.
On Thu, 2006-09-21 at 09:19 -0400, Lamar Owen wrote:
On Wednesday 20 September 2006 11:12, Les Mikesell wrote:
On Wed, 2006-09-20 at 09:41 -0500, Erick Perez wrote:
Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
You can't reconnect to a broken ssh connection, and in fact it should have killed all the processes you were running.
Unfortunately, I have seen many instances where ssh sessions do like this; if one happens to be running a yum update in one, and yum is downloading packages (putting yum into its unkillable mode, which, in my opinion is such an annoying thing; there have been a number of times I'd start up an update, have it run for a while, then need to leave (taking my laptop with me, and thus disconnecting the session, which can cause its own problems) where I'd like to just simply CTRL-C yum and have it do the Right Thing; yum just cycles to the next mirror (at least the last time a couple of weeks ago it did this) when you hit CTRL-C OR when you send yum a SIGTERM)), then you can get some really wierd artifacts with unkillable but not running yum processes; I have seen a few where SIGKILL didn't do anything, and all because of a network glitch.
--- man screen
screen creates a detachable session
Craig
On Thu, 2006-09-21 at 06:29 -0700, Craig White wrote:
Hi, is there a way to "reconnect" to a ssh session that was disconnected and left running processes in the linux server?
You can't reconnect to a broken ssh connection, and in fact it should have killed all the processes you were running.
Unfortunately, I have seen many instances where ssh sessions do like this; if one happens to be running a yum update in one, and yum is downloading packages (putting yum into its unkillable mode, which, in my opinion is such an annoying thing; there have been a number of times I'd start up an update, have it run for a while, then need to leave (taking my laptop with me, and thus disconnecting the session, which can cause its own problems) where I'd like to just simply CTRL-C yum and have it do the Right Thing; yum just cycles to the next mirror (at least the last time a couple of weeks ago it did this) when you hit CTRL-C OR when you send yum a SIGTERM)), then you can get some really wierd artifacts with unkillable but not running yum processes; I have seen a few where SIGKILL didn't do anything, and all because of a network glitch.
man screen
screen creates a detachable session
Or, depending on your bandwidth and how you feel about GUI's, look at VNC (using the module to export your console screen or vncserver for separate long-running sessions).
Or, depending on your bandwidth and how you feel about GUI's, look at VNC (using the module to export your console screen or vncserver for separate long-running sessions).
I thouroughly enjoy using the FreeNX software to connect to sessions. IMHO cleaner and faster then VNC and RDP, plus uses ssh for the port access so no extra firewall rules or services directly accessible.
-- Les Mikesell lesmikesell@gmail.com
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2006-09-21 at 12:32, Trevor Benson wrote:
Or, depending on your bandwidth and how you feel about GUI's, look at VNC (using the module to export your console screen or vncserver for separate long-running sessions).
I thouroughly enjoy using the FreeNX software to connect to sessions. IMHO cleaner and faster then VNC and RDP, plus uses ssh for the port access so no extra firewall rules or services directly accessible.
I agree freenx is very nice, but I've had trouble reconnecting to sessions, especially from clients with different screen sizes. Maybe that's been fixed in recent updates, but sometimes the session you want to pick up remotely is the one you left running on the console and I think the vnc module for X is the only way you can do that - and you can tunnel the connection through ssh if you want.
On Thursday 21 September 2006 09:29, Craig White wrote:
man screen
screen creates a detachable session
Yes, I know. I've used it and dtach both. And it's usually the case that when I need to detach and reattach is typically when I've not run screen or dtach prior. Typically when I do run them, I haven't needed them; like any thing, it needs to become a habit, and I've just not made it a habit as yet.
dtach is quite a bit simpler and smaller than screen; it doesn't, of course, do as much either.
Hi Erick:
General but good info about screen use: http://www.linuxjournal.com/article/6340
I hope it will be useful for you.
-
Craig White -
Erick Perez -
Jordi Espasa Clofent -
Lamar Owen -
Les Mikesell -
Morten Torstensen -
Scott Silva -
Steve Huff -
Trevor Benson