[Paraview] paraview - client-server

[Sean Ziegeler]

Both ways will work for me in most cases, i.e. a "forward" connection 
with ssh -L or a reverse connection with ssh -R.

However, I find that the reverse method is more scriptable.  You can set 
up a .pvsc file that the client can load and will call ssh with the 
appropriate options and commands for the remote host, all from the GUI. 
  The client will simply wait for the reverse connection from the 
server, whether it takes 5 seconds or 5 hours for the server to get 
through the batch queue.

Using the forward connection method, if the server isn't started soon 
enough, the client will attempt to connect and then fail.  I've always 
had to log in separately, wait for the server to start running, then 
tell my client to connect.

-Sean

On 02/06/10 12:58, burlen wrote:
> Hi Pat,
>
> My bad. I was looking at the PV wiki, and thought you were talking about
> doing this without an ssh tunnel and using only port forward and
> paraview's --reverse-connection option . Now that I am reading your
> hpc.mil post I see what you mean :)
>
> Burlen
>
>
> pat marion wrote:
>> Maybe I'm misunderstanding what you mean by local firewall, but
>> usually as long as you can ssh from your workstation to the login node
>> you can use a reverse ssh tunnel.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview