On Mon, May 11, 2020 at 09:39:26PM +0000, Mun Johl wrote: > Hi William, > > Thank you for your reply. > See my comments below. > > > -----Original Message----- > > On Thu, May 07, 2020 at 06:29:05PM +0000, Mun Johl wrote: > > > Hi William, et al., > > > I am not explicitly setting the DISPLAY--as that is how I normally use > > > 'ssh -X'. Nor have I done anything to open any additional ports. > > Again, since 'ssh -X' is working for us. As a reminder, there is no way > > for me to know what to set DISPLAY to even if I wanted to set it. > > > > > Do you invoke qrsh with -V by any chance? I think that might cause the > > DISPLAY from the login node to override the one set by ssh -X. If you > > do could you switch to using -v to transfer individual environment > > variables instead? > > [Mun] Yes, I do use -V normally. When I once again get to a point where qrsh > is able to launch I will certain try your suggestion. But I may tweak it by > simply "unset'ing" DISPLAY from the wrapper script rather than using -v > because we have many env vars that are required in order to correctly run a > job. The problem with unsetting DISPLAY is that if you do it then ssh won't be able to forward it.
Possibly env -u DISPLAY XDISPLAY="${DISPLAY}" qrsh -now n -V <command>
Then a wrapper around ssh as your qrsh_command
#!/bin/sh
env DISPLAY="${XDISPLAY}" /usr/bin/ssh -X "$@"
signature.asc
Description: PGP signature
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
