public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Andrew Braverman" <abraverman@itms.com>
To: <cygwin-xfree@cygwin.com>
Cc: <bszk@wright.aps.uoguelph.ca>, <bo@uoguelph.ca>
Subject: RE: Initiating a remote X session
Date: Wed, 21 Jan 2004 16:25:00 -0000 [thread overview]
Message-ID: <000f01c3e03b$34a18a00$1e54cea7@andrew> (raw)
In-Reply-To: <Pine.LNX.4.58.0401211635360.12066@odoaker.hrz.tu-chemnitz.de>
I would also suggest ssh tunnels for what you are trying to do. That is
what I do myself. If you
really do not want to do that, a replacement for
MYIP=`hostname -i` rexec <host> -l <username> "setenv DISPLAY $MYIP:0;
/opt/SAS82/sas"
might be
MYIP=`ipconfig | grep "IP Address" | awk '{print $NF}'` rexec <host> -l
<username> "setenv DISPLAY $MYIP:0; /opt/SAS82/sas"
This assumes that there is only one network interface on the machine and the
machine has all the requisite programs installed. I know that the Windows
9x versions had a program called winipcfg, which could not be used this way.
I am not sure if they had ipconfig in those versions and if not, when it
started.
Andy
> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Alexander Gottwald
> Sent: Wednesday, January 21, 2004 10:41 AM
> To: cygwin-xfree@cygwin.com
> Cc: bszk@wright.aps.uoguelph.ca; bo@uoguelph.ca
> Subject: Re: Initiating a remote X session
>
>
> On Wed, 21 Jan 2004, Steve Howie wrote:
>
> > Howdy,
> >
> > We've just had a look at cygwin-xfree and are very
> impressed. However,
> > we'd like to bundle it for our users so that we have a some
> pre-defined
> > 'sessions' available e.g. connect to a Unix host, run SAS
> then have the
> > output sent to an cygwin-xfree server. Unix commands are
> not the forte
> > of most of our users.
> >
> > This is fine with a static IP address - we would launch a
> program which
> > does something like:
> >
> > rexec <host> -l <username> "setenv DISPLAY <ipaddress>;
> /opt/SAS82/sas "
>
> > So ideally we would like something similar to this in cygwin-xfree :
> >
> > rexec <host> -l <username> "setenv DISPLAY $MYIP:0; /opt/SAS82/sas"
>
> First try:
> MYIP=`hostname -i` rexec <host> -l <username> "setenv
> DISPLAY $MYIP:0; /opt/SAS82/sas"
>
> but hostname -i does not work on cygwin. But maybe the name
> of the host is
> sufficient
> MYIP=`hostname` rexec <host> -l <username> "setenv DISPLAY
> $MYIP:0; /opt/SAS82/sas"
>
> Or even better, Use ssh:
>
> DISPLAY=localhost:0 ssh -X <host> -l <username> "/opt/SAS82/sas"
>
> ssh will take care of setting the remote DISPLAY and all transferred
> data is sent via the ssh tunnel.
>
> bye
> ago
> --
> Alexander.Gottwald@s1999.tu-chemnitz.de
> http://www.gotti.org ICQ: 126018723
>
next prev parent reply other threads:[~2004-01-21 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 15:31 Steve Howie
2004-01-21 15:41 ` Alexander Gottwald
2004-01-21 16:24 ` Steve Howie
2004-01-21 17:10 ` Alexander Gottwald
2004-01-21 17:42 ` Benjamin Riefenstahl
2004-01-21 16:25 ` Andrew Braverman [this message]
2004-01-21 16:46 ` Chris Green
2004-01-22 9:30 ` Hans Dekker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000f01c3e03b$34a18a00$1e54cea7@andrew' \
--to=abraverman@itms.com \
--cc=bo@uoguelph.ca \
--cc=bszk@wright.aps.uoguelph.ca \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).