Tunnelling X for R graphics

[....]
	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 24 hours and thus the ssh session dies.
Is it possible to do anything about the VPN software?  I use tightVNC
to do something similar and it doesn't time out after 24 hours.  Even
closing the desktop machine down altogether does not lose the ssh
connexion.  Restarting the desktop a week later will still find the X
session without loss.

HTH
~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.   
   ___    Patrick Connolly   
 {~._.~}                   Great minds discuss ideas    
 _( Y )_  	         Average minds discuss events 
(:_~*~_:)                  Small minds discuss people  
 (_)-(_)  	                      ..... Eleanor Roosevelt

~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.

	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 24 hours and thus the ssh session dies.
Is it possible to do anything about the VPN software?  I use tightVNC to
do something similar and it doesn't time out after 24 hours.  Even closing
the desktop machine down altogether does not lose the ssh connexion. 
Restarting the desktop a week later will still find the X session without
loss.
The VPN software is managed and maintained by the company I'm doing
statistical computing work for...out of my control. Your comments about
TightVNC are pretty impressive, though--I'm not really sure how that would
work...though if you set your ssh connection to not push any data towards
your computer, I gather the server would have no reason to believe you were
unresponsive?

In any case, this sadly doesn't help me, but many thanks!

For now, I'm just trying my hardest to remeber to dev.off() when I'm done
using graphics.

--Adam
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 connection gives you).

The warning comes from any X erorr, and it is not possible to know how 
serious it is without external information.

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 24 hours and thus the ssh session dies.
Is it possible to do anything about the VPN software?  I use tightVNC to
do something similar and it doesn't time out after 24 hours.  Even closing
the desktop machine down altogether does not lose the ssh connexion. 
Restarting the desktop a week later will still find the X session without
loss.
The VPN software is managed and maintained by the company I'm doing
statistical computing work for...out of my control. Your comments about
TightVNC are pretty impressive, though--I'm not really sure how that would
work...though if you set your ssh connection to not push any data towards
your computer, I gather the server would have no reason to believe you were
unresponsive?

In any case, this sadly doesn't help me, but many thanks!

For now, I'm just trying my hardest to remeber to dev.off() when I'm done
using graphics.

--Adam

______________________________________________
R-help at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595
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

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 connection 
gives you).

The warning comes from any X erorr, and it is not possible to know how 
serious it is without external information.

On Mon, 2 Feb 2009, Adam D. I. Kramer wrote:

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 24 hours and thus the ssh session dies.
Is it possible to do anything about the VPN software?  I use tightVNC to
do something similar and it doesn't time out after 24 hours.  Even closing
the desktop machine down altogether does not lose the ssh connexion. 
Restarting the desktop a week later will still find the X session without
loss.
The VPN software is managed and maintained by the company I'm doing
statistical computing work for...out of my control. Your comments about
TightVNC are pretty impressive, though--I'm not really sure how that would
work...though if you set your ssh connection to not push any data towards
your computer, I gather the server would have no reason to believe you were
unresponsive?

In any case, this sadly doesn't help me, but many thanks!

For now, I'm just trying my hardest to remeber to dev.off() when I'm done
using graphics.

--Adam

______________________________________________
R-help at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide 
http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

-- 
Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595

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 structure 
'display'.  It is the latter that needs to be reinitialized.
I'll reply again to this post if I find other parts of R working poorly
after the disconnection.

--Adam

On Tue, 3 Feb 2009, Prof Brian Ripley wrote:

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 connection gives you).

The warning comes from any X erorr, and it is not possible to know how 
serious it is without external information.

On Mon, 2 Feb 2009, Adam D. I. Kramer wrote:

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 24 hours and thus the ssh session 
dies.
Is it possible to do anything about the VPN software?  I use tightVNC to
do something similar and it doesn't time out after 24 hours.  Even 
closing
the desktop machine down altogether does not lose the ssh connexion. 
Restarting the desktop a week later will still find the X session without
loss.
The VPN software is managed and maintained by the company I'm doing
statistical computing work for...out of my control. Your comments about
TightVNC are pretty impressive, though--I'm not really sure how that would
work...though if you set your ssh connection to not push any data towards
your computer, I gather the server would have no reason to believe you 
were
unresponsive?

In any case, this sadly doesn't help me, but many thanks!

For now, I'm just trying my hardest to remeber to dev.off() when I'm done
using graphics.

--Adam

______________________________________________
R-help at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide 
http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

-- 
Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595

Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595