Re: Initiating a remote X session
Hi Steve,
Being triggered when you mentioned you are using SAS, here is another
solution that may help you. You can change the scripts with secure
shells as you like.
We are using sas too. I have installed cygwin to be able to remotely use
it, which works fine apart from some nitty gritty AltGr keyboard
problems I have and you probably don't when using US keyboards.
I used the following set up to give access to users on the Unix
containing Sas:
The startxwin.bat is modified to:
start XWin -multiwindow
xterm -T SAS startup window -e \\Your server\Central
directory\initsas.sh %1%
The server and central directory are accesible to anyone using Sas.
Now, the contents of initsas.sh are:
xhost +sas server /dev/null
echo Starting SAS environment...
export IPADDR=`ipconfig | grep ddress | grep 10\. | cut -f 2 -d : |
cut -f 2 -d `
rsh sas server -l ${USERNAME} export DISPLAY=\${IPADDR}:0.0\;cd
/opt/sas8;sas ${1}
Please note that:
1. The usernames for WinXP domains are the same as those used on Unix.
2. The WinXP client is given access to the Unix/Sas host by putting the
IP-number/client name in the hosts.equiv.
3. Different versions of Windows give you different formats of ipconfig
output.
4. Our Ip-addresses start with 10.
5. As a parameter to the startxwin.bat we use '-explorer', to be used as
a sas startup parameter.
See your sas documentation for more options.
Hope it helps you,
H.
Steve Howie escribió:
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
from the Cygwin shell. All bets are off, however, since most of our IP
addresses are served out by DHCP.
We currently use X-Win32 which has a nifty feature for getting around
this - you can specify $MYIP:0 which picks up the current IP address of
the X-server and passes it to the session definition which is sent to
the host which will run the application.
So ideally we would like something similar to this in cygwin-xfree :
rexec host -l username setenv DISPLAY $MYIP:0; /opt/SAS82/sas
I did a quick dig through the archives and noticed something similar to
this question - but it was from a while ago - we'd ideally like to have
the user get a popup prompting them for a username/password for the
host, then pass this information via a command such as the one above,
and also pick up the X-servers IP address whether static or dynamic. Is
something like this available already?
Any info would be appreciated!
Thanks,
Scotty
---
Steve Howie
Academic Services, CCS
University of Guelph
Guelph Ontario
CANADA
.
RE: non-widget child DropSiteManager error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... )
On Wed, 21 Jan 2004, Brian Ford wrote:
I have my new machine set up now, so I'll try to take a stab at compiling
it myself today. I'll let you know how I make out. Thanks for being
patient.
It compiled for me (including DLLs) almost out of the box. I did make the
following change to lesstif-0.93.91-6.sh. I am not sure that the change
was required, because I did not try without it. But, it felt like a
better idea to me :^D.
In the prep rule, remove all the autotool stuff between:
touch INSTALL \
and
rm -f INSTALL )
replacing it simply with:
autoreconf --install --force \
so it reads:
prep() {
(cd ${topdir} \
tar xv${opt_decomp}f ${src_orig_pkg} ; \
cd ${topdir} \
patch -p0 ${src_patch}
mkdirs ) \
(cd ${srcdir} \
touch INSTALL \
autoreconf --install --force \
rm -f INSTALL )
}
To do a debug build, just look at the target all:
all) prep conf build install \
strip pkg spkg finish ; \
STATUS=$? ;;
and do everything but the strip step.
Let me know if this doesn't work for you.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
XFree86-xserv 4.3.0-42, Alt Gr, clipboard, accents...
Hi, I have updated to version 4.3.0-42 of XFree86-xserv. I am using Windows XP and a French keyboard. Here are the results: Alt Gr key works with the standard startxwin.sh for Sun Solaris 9 clients, but not for Solaris 7 clients. For Solaris 7 clients, setxkbmap fr changes nothing, neither does a /etc/X11/XF86Config file. For Solaris 7 clients, I run xmodmap with these commands: clear Mod5 keycode 113 = Mode_switch add Mod3 = Mode_switch keycode 10 = ampersand 1 keycode 11 = eacute 2 asciitilde keycode 12 = quotedbl 3 numbersign keycode 13 = apostrophe 4 braceleft keycode 14 = parenleft 5 bracketleft keycode 15 = minus 6 bar keycode 16 = egrave 7 grave keycode 17 = underscore 8 backslash keycode 18 = ccedilla 9 asciicircum keycode 19 = agrave 0 at keycode 20 = parenright degree bracketright keycode 21 = equal plus braceright In order to copy and paste text between X clients and Windows programs, I still have to specify -clipboard in the XWin command of the startxwin.sh script (it is not yet the standard argument). Selected text in X clients now stays highlighted. The accented characters on the French keyboard work correctly: e-acute, e-grave, c-cedilla, a-grave, u-grave. The accented characters obtained by pressing first the accent (circumflex, diaresis) and then the letter work for cygwin X clients, for not for Solaris 7 or Solaris 9 X clients. The accented characters with tilde work for the cygwin shell, but not for cygwin or Solaris X clients. I haven't included the accented characters because the message gets blocked, considered as Spam! Thanks to Harold for all the work! Philippe Auclair ** Institut National de la Recherche Agronomique Unité Centrale Informatique de Jouy Domaine de Vilvert, 78352 Jouy-en-Josas CEDEX, France [EMAIL PROTECTED] tel +33 1 34 65 26 95, fax +33 1 34 65 24 03 **
RE: Startx on WinXP
On Wed, 21 Jan 2004, Brian L. Walter wrote: the *solution* was a cheat. I commented out the references in startx to $HOME. Since I don't have specific configurations, this is an acceptable white lie. Why not try startxwin.bat and the nifty multiwindow mode (ie. Windows is the window manager)? The version of lesstif is 0.93.91-6. Interestingly enough, it's -2 on the win98 machine, on which mwm *does* work. I might try downgrading to -2 (from the install packages on the win98 machine). WFM. -2 was a broken attempt at an Xm DLL. It just so happened that mwm was still linked to the static Xm in that package. In general, it was broken, so don't revert please. You might post strace mwm | grep Mwm 21 to see if it is an app-default issue. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Crash in xserv 4.3.0-42
I have not been able to reproduce the access violation in xserv 4.3.0-42. Rejoice! Øyvind
Re: win-ssh-askpass not working.
Steve Howie wrote: Can't get it to work - set up the win-ssh-agent, ran the ssh command from a script after setting the DISPLAY and SSH_ASKPASS environment variables and SSH still prompted me for a password - no askpass window popped up. Any ideas?? Running on Windows XP Professional. Script (as suggested by Alexander Gottwald): #!/bin/bash export DISPLAY=localhost:0.0 export SSH_ASKPASS=/usr/bin/win-ssh-askpass.exe ssh -f -X host -l username /opt/SAS82/sas I've done some test on it yesterday and it showed that the askpass program is only executed when the ssh has no terminal. On linux I could start the ssh from gvim and the it started x11-ssh-askpass. But on windows ssh was always started in a console window. Maybe the run.exe utility might help. But I've never used it and have no links and further information on it. run.exe will start programs without console windows. Then ssh has no terminal and it must start win-ssh-askpass. bye ago NP: Tristesse De La Lune - Eiskalte Liebe -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: win-ssh-askpass not working.
On Thu, 22 Jan 2004, Alexander Gottwald wrote: Steve Howie wrote: Can't get it to work - set up the win-ssh-agent, ran the ssh command from a script after setting the DISPLAY and SSH_ASKPASS environment variables and SSH still prompted me for a password - no askpass window popped up. Any ideas?? Running on Windows XP Professional. Script (as suggested by Alexander Gottwald): #!/bin/bash export DISPLAY=localhost:0.0 export SSH_ASKPASS=/usr/bin/win-ssh-askpass.exe ssh -f -X host -l username /opt/SAS82/sas I've done some test on it yesterday and it showed that the askpass program is only executed when the ssh has no terminal. On linux I could start the ssh from gvim and the it started x11-ssh-askpass. But on windows ssh was always started in a console window. Maybe the run.exe utility might help. But I've never used it and have no links and further information on it. run.exe will start programs without console windows. Then ssh has no terminal and it must start win-ssh-askpass. IIUC, that's exactly what the setsid command is intended to accomplish. You can also try using bash's disown builtin. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
