In an ssh client, under connections section, there is an option for
tunneling. Please ensure that the tunneling options are turned on.. and if
applicable, incoming/outgoing tunnels, listen/destination ports, etc. are
set.
Thanks,
Santosh
On Tue, Feb 3, 2009 at 2:03 PM, Adam D. I. Kramer wrote:
>
On Tue, 3 Feb 2009, Adam D. I. Kramer wrote:
Thanks very much for the reassurance.
Really, I can just open a new X11 device on the same display, since the
display (localhost:10) is effectively "reconnected" when I ssh in again.
We are not taiking about the DISPLAY variable, but the X11 struct
Thanks very much for the reassurance.
Really, I can just open a new X11 device on the same display, since the
display (localhost:10) is effectively "reconnected" when I ssh in again.
I'll reply again to this post if I find other parts of R working poorly
after the disconnection.
--Adam
On Tue,
To answer your basic question, you do need to shut down everything
involivng X, that is X11() devices and the X11 dataeditor. If you do
that (and graphics.off() will suffice for the first), you should be
able to re-open an X11 device on another display (which is what
presumably a new VNC conne
On Tue, 3 Feb 2009, Patrick Connolly wrote:
The problem, and maybe I'm just whining here, is that because the
data sets are large this takes several minutes where I'm basically just
sitting around. This happens once every other day as the VPN software
I'm using "times out" after about
Indeed, I am running R in screen. That is the context in which this error
occurs.
The problem is that screen passes $DISPLAY as the $DISPLAY for the actual
terminal. So when the ssh session dies, the X11 connection is broken.
The REST of R works fine...which is why I use screen in the first plac
On Sat, 31-Jan-2009 at 03:16PM -0800, Adam D. I. Kramer wrote:
[]
> The problem, and maybe I'm just whining here, is that because the
> data sets are large this takes several minutes where I'm basically just
> sitting around. This happens once every other day as the VPN software I'm
>
On Saturday 31 January 2009, Erik Iverson wrote:
> Dylan,
>
> Can you confirm that you've done that before while tunneling R graphics
> over ssh? I thought I'd tried and screen and failed with a similar message
> when using graphics as Adam had. I could be wrong though.
Ack. Maybe I spoke too so
Dylan,
Can you confirm that you've done that before while tunneling R graphics over
ssh? I thought I'd tried and screen and failed with a similar message when
using graphics as Adam had. I could be wrong though.
Dylan Beaudette wrote:
Try starting your R session after starting a 'screen' s
Try starting your R session after starting a 'screen' session. Like this:
$> screen
$> R
# do stuff, when taking a break do CTRL-A D to disconnect
# use as normal
See the man page for screen, it is basically a terminal multiplexer
that can gracefully accommodate connection failures. If you get
di
Dear colleagues,
I run R on a few different machines, and view graphs and the like by
tunnelling X through SSH to my local machine. This is useful for me because
my local machine can't easily handle some of the data sets I work with.
However, when an ssh connection dies, the tunn
11 matches
Mail list logo
