On 05/22/2015 01:38 PM, Burlen Loring wrote:
Hi Jeff,
It really sounds like you are unintentionally using X forwarding. It
could be baked into your ssh config or a bash alias.
After some digging, it appears X forwarding is configured on in our ssh
config. I got it to work by explicitly using
Hi Jeff,
It really sounds like you are unintentionally using X forwarding. It
could be baked into your ssh config or a bash alias.
I see the window with the gears
if you are really doing remote rendering, you won't see the window.
you may be able to confirm accidental X forward using ssh with
On 05/22/2015 07:28 AM, Utkarsh Ayachit wrote:
Jeff,
Can you make sure the "Remote Render Threshold" is set to 0?
It is
Also, do you have an X server running (and accessible) on the backend
nodes? You're not using "ssh -X" to login to the backend nodes, right?
I do start an X server on the
Jeff,
Can you make sure the "Remote Render Threshold" is set to 0?
Also, do you have an X server running (and accessible) on the backend
nodes? You're not using "ssh -X" to login to the backend nodes, right?
On Thu, May 21, 2015 at 4:54 PM, Jeff Becker wrote:
> Hi. I created a VTK unstructured
Hi. I created a VTK unstructured grid (.vtu) file for a 500 by 500 by
500 point data set. In order to visualize it, I fire up 8 pvservers on
my GPU multicore backend node using:
mpirun -np 8 pvserver --client-host=XXX --use-offscreen-rendering
and connect to the root server from my ParaView c
