Then the dropped ssh connection had not caused the ssh daemon to terminate
yet, and the screen session was still attached... usually screen only
offers to reattach detached sessions.
Well, that's the point of screen, it doesn't terminate when parent
terminates. Plus you can detach screen that
On Mon, Mar 26, 2007 at 06:48:00PM -0400, Jim Hyslop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrique de Moraes Holschuh wrote:
Not even screen -rda worked?
Woohoo! That's got it, thanks.
Now I just have to remember to use screen whenever I'm about to do
anything I
On Sun, 25 Mar 2007 22:42:38 -0300
Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote:
On Sun, 25 Mar 2007, Jim Hyslop wrote:
Yes, that's what I did. I started an ssh session, ran 'screen', and
launched a program (man screen, IIRC). I got two or three screens
running, and was able to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrique de Moraes Holschuh wrote:
Not even screen -rda worked?
Woohoo! That's got it, thanks.
Now I just have to remember to use screen whenever I'm about to do
anything I don't want disconnected :-)
- --
Jim Hyslop
Dreampossible: Better
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kamaraju S Kusumanchi wrote:
Is there any firewall between the server and the client? If so, the firewall
might be switching off the idle ssh connections. If this infact is your
problem, to keep the ssh connections alive use ServerAliveInterval
On Mon, 26 Mar 2007, Jim Hyslop wrote:
Henrique de Moraes Holschuh wrote:
Not even screen -rda worked?
Woohoo! That's got it, thanks.
Then the dropped ssh connection had not caused the ssh daemon to terminate
yet, and the screen session was still attached... usually screen only
offers to
On Sat, Mar 24, 2007 at 08:50:59PM -0400, Jim Hyslop wrote:
Henrique de Moraes Holschuh wrote:
but you
might want to look at the screen program (see package screen) for the
next time you need terminals you want to reattach to.
Thanks for the suggestion. It didn't work, unfortunately.
On Fri, 23 Mar 2007 16:52:25 -0400
Jim Hyslop [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, gang
I suspect I know the answer to this, but I'm going to ask anyway :-)
When I ssh into my Debian box from my laptop, sometimes I step away from
the laptop, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Smith wrote:
On Sat, Mar 24, 2007 at 08:50:59PM -0400, Jim Hyslop wrote:
Thanks for the suggestion. It didn't work, unfortunately. 'screen -r
pts-0.sirius' returns the error There is no screen to be resumed
matching pts-0.sirius.
You need
On Sun, 25 Mar 2007, Jim Hyslop wrote:
Yes, that's what I did. I started an ssh session, ran 'screen', and
launched a program (man screen, IIRC). I got two or three screens
running, and was able to switch between them.
Then I put my laptop into standby, and brought it out, which forced the
Jim Hyslop wrote:
When I ssh into my Debian box from my laptop, sometimes I step away from
the laptop, and when I come back it's gone into standby. This, of
course, drops the TCP/IP connection to the Debian box. Is there any way
to re-establish the connection to the session I was running? If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrique de Moraes Holschuh wrote:
On Fri, 23 Mar 2007, Jim Hyslop wrote:
course, drops the TCP/IP connection to the Debian box. Is there any way
to re-establish the connection to the session I was running? If I try
ssh again, I get a new TTY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, gang
I suspect I know the answer to this, but I'm going to ask anyway :-)
When I ssh into my Debian box from my laptop, sometimes I step away from
the laptop, and when I come back it's gone into standby. This, of
course, drops the TCP/IP
On Fri, 23 Mar 2007, Jim Hyslop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, gang
I suspect I know the answer to this, but I'm going to ask anyway :-)
When I ssh into my Debian box from my laptop, sometimes I step away from
the laptop, and when I come back it's gone into standby.
On Fri, 23 Mar 2007, Jim Hyslop wrote:
course, drops the TCP/IP connection to the Debian box. Is there any way
to re-establish the connection to the session I was running? If I try
ssh again, I get a new TTY session.
I don't know if you can reconnect to the old tty (if ssh noticed the
15 matches
Mail list logo