[Paraview-developers] xterm -e ssh for windows and mac

Wed Sep 21 21:40:12 EDT 2016

Connect->Fetch to download the "windows to *@anl" or "windows to *@ornl"
configs to see how I set it up there. You'll find that::

xterm -hold -e ssh -R s_port:localhost:c_port user at host
/remote/machines/path/to/launch.sh

is replaced with

/C start cmd.exe "C:\Program Files (x86)\PuTTY\plink.exe"  -ssh host -R
s_port:localhost:c_port -l user /remote/machines/path/to/launch.sh

start is more or less like "&" on linux
cmd.exe is like xterm
plink is like ssh

Andy recently slipped in kerberos without any difficulty so I know that can
work too.

As I recall on mac and linux the terminal sticks around until you exit the
paraview client and if you kill it beforehand the connection dies. On
windows the terminal sticks around even after paraview client dies so you
have to manually kill it.

My preference is to work out the licensing issues and package libssh within
ParaView and replace the terminal call with a suitably secure qt dialog.
Then it would all be standalone.

On Sep 21, 2016 7:44 PM, "Scott, W Alan" <wascott at sandia.gov> wrote:

> Sounds good.  We have an acceptable Mac solution.
>
>
>
> Utkarsh?  Windows?
>
>
>
> Alan
>
>
>
> *From:* Moreland, Kenneth
> *Sent:* Wednesday, September 21, 2016 5:42 PM
> *To:* Scott, W Alan <wascott at sandia.gov>; paraview-developers at paraview.org
> *Cc:* Patchett, John M. (LANL) <patchett at lanl.gov>; Angelini, Richard C
> USA CIV (US) (richard.c.angelini.civ at mail.mil) <
> richard.c.angelini.civ at mail.mil>; Cone, Giovanni Antonio (LANL) <
> conega at lanl.gov>
> *Subject:* RE: [Paraview-developers] xterm -e ssh for windows and mac
>
>
>
> All in all, having the terminal stick around seems like a minor
> inconvenience. Plus if it bothers a user they can change the settings to
> close the terminal windows automatically (http://superuser.com/question
> s/16470/how-can-i-make-the-terminal-window-close-automatically-on-os-x).
>
>
>
> -Ken
>
>
>
> *From:* Scott, W Alan
> *Sent:* Wednesday, September 21, 2016 4:41 PM
> *To:* Moreland, Kenneth <kmorel at sandia.gov>;
> paraview-developers at paraview.org
> *Cc:* Patchett, John M. (LANL) <patchett at lanl.gov>; Angelini, Richard C
> USA CIV (US) (richard.c.angelini.civ at mail.mil) <
> richard.c.angelini.civ at mail.mil>; Cone, Giovanni Antonio (LANL) <
> conega at lanl.gov>
> *Subject:* RE: [Paraview-developers] xterm -e ssh for windows and mac
>
>
>
> I haven’t tried Putty, but that is a good idea.  Even if we don’t include
> Putty with the binaries, we could at least document how to get it and add
> it into the ParaView tree.
>
>
>
> Yes, Terminal works for Mac.  The one thing I don’t like about it is that
> it is impossible to close the terminal automagically when you are done.
> The user has to manually close it.
>
>
>
> Alan
>
>
>
> *From:* Moreland, Kenneth
> *Sent:* Wednesday, September 21, 2016 4:29 PM
> *To:* Scott, W Alan <wascott at sandia.gov>; paraview-developers at paraview.org
> *Cc:* Patchett, John M. (LANL) <patchett at lanl.gov>; Angelini, Richard C
> USA CIV (US) (richard.c.angelini.civ at mail.mil) <
> richard.c.angelini.civ at mail.mil>; Cone, Giovanni Antonio (LANL) <
> conega at lanl.gov>
> *Subject:* RE: [Paraview-developers] xterm -e ssh for windows and mac
>
>
>
> Here are a couple of simple solutions that might be easier than implement
> our own ssh client in ParaView.
>
>
>
> For Windows: Consider putty (http://www.putty.org/). It is a small (and I
> believe reasonably well maintained) ssh client for Windows. It opens its
> own terminal window, so entering username/password is not a concern. It
> could be distributed with binaries, although I would consult a lawyer
> before exporting it outside the U.S.
>
>
>
> For Mac: Mac comes with ssh. It also comes with the “Termial” program that
> allows you to run programs and interact with standard input and output with
> X11 running. The trick is just to run ssh from within the Terminal program.
> You should be able to do that by creating a shell script with the extension
> “.command” that calls ssh how you want it. Then make the script executable
> (chmod a+x …) and invoke it with the open command (which also comes with
> Mac OS).
>
>
>
> -Ken
>
>
>
> *From:* Paraview-developers [mailto:paraview-developers-bo
> unces at paraview.org <paraview-developers-bounces at paraview.org>] *On Behalf
> Of *Scott, W Alan
> *Sent:* Wednesday, September 21, 2016 3:25 PM
> *To:* paraview-developers at paraview.org
> *Cc:* Patchett, John M. (LANL) <patchett at lanl.gov>; Angelini, Richard C
> USA CIV (US) (richard.c.angelini.civ at mail.mil) <
> richard.c.angelini.civ at mail.mil>; Cone, Giovanni Antonio (LANL) <
> conega at lanl.gov>
> *Subject:* [EXTERNAL] [Paraview-developers] xterm -e ssh for windows and
> mac
>
>
>
> As I mentioned at our Sandia/ LANL/Kitware quarterly, we need some
> solution in order to allow users to connect Windows and OSX ParaView to
> pvserver running on a cluster.  It needs to be better than our current
> solution of arm waving and ignoring the issue.  On Linux, this is done with
> an xterm and ssh.  Currently, Sandia has a custom solution (that is out of
> date and hard to build). I would rather have a common solution, and the
> global user community needs a solution.
>
>
>
> To start the discussion, I see one of two paths we can take:
>
> ·         Kitware provide a solution built into ParaView.
>
> ·         Kitware provide detailed instructions on the Wiki for users to
> build this themselves.
>
>
>
> Where do we go from here?
>
>
>
> Alan
>
>
>
> p.s. – I think I included everyone needed for the discussion.  If I missed
> anyone, feel free to add them.
>
>
>
> --------------------------------------------------------
>
> W. Alan Scott
>
> ParaView Support Manager
>
>
>
> SAIC
>
> Sandia National Laboratories, MS 0822
>
> Org 9326 - Building 880 A1-K
>
> (505) 284-0932   FAX (505) 284-5619
>
> ---------------------------------------------------------
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=
> Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20160921/e9bcc4c1/attachment-0001.html>