On Apr 15, 05 12:53:02 +0200, Joakim Ahlén wrote:
> I'll try that. You can probably reproduce the error yourself by reseting
> your (not the servers) network connection in a way which doesn't send an
> ICMP reset to the server. Just yanking out your cable probably might work
> depending on your loc
> On Apr 15, 05 11:46:00 +0200, Joakim Ahlén wrote:
> > > > * Run screen -d -r, which hangs. Leave it hanging.
> > > > * Start up another SSH session, and su to root
> > > > * Find the PID of the SCREEN-process (with capitals), and
> > > run "strace
> > > > -p [pid of SCREEN] 2>/dev/null"
> > >
>
On Apr 15, 05 11:46:00 +0200, Joakim Ahlén wrote:
> > > * Run screen -d -r, which hangs. Leave it hanging.
> > > * Start up another SSH session, and su to root
> > > * Find the PID of the SCREEN-process (with capitals), and
> > run "strace
> > > -p [pid of SCREEN] 2>/dev/null"
> >
> > what would
On Apr 15, 05 10:11:13 +0200, Joakim Ahlén wrote:
> However, i do have a foolproof way of getting back control of the screen. It
> may sound really obscure - but it works EVERY time.
>
> * Run screen -d -r, which hangs. Leave it hanging.
> * Start up another SSH session, and su to root
> * Find th
Hi,
> On Apr 15, 05 10:11:13 +0200, Joakim Ahlén wrote:
> > However, i do have a foolproof way of getting back control of the
> > screen. It may sound really obscure - but it works EVERY time.
> >
> > * Run screen -d -r, which hangs. Leave it hanging.
> > * Start up another SSH session, and su t
Hi everyone,
I have been experiencing this bug for i guess a year or two and im dead
tired of it. Apparently others have the same problem. From reading this
thread and combining it with my own experience about it, my conclusion of
the problem is:
* You use SSH to connect to a machine in which you
