Thanks to
Anselmo Elcana de Oliveira <elcana_at_IQM.Unicamp.BR> and
Wesley Darlington <w.darlington_at_am.qub.ac.uk>
for their help.
We also enlisted help configuring Xvision from Xvision itself. We configured
Xvision to attach to the host via rlogin method. The Xvision software wanted a
command to execute on the host. We created a script in the user's home
directory :
/usr/bin/X11/xterm&
set DISPLAY hostname_of_pc:0
export DISPLAY
/usr/dt/bin/Xsession
which was the startup command. This started an xterminal session in the
background and then fired up a CDE session. There are a number of configuration
parameters for Xvision which must also be satisfied.
------------------------------------------------------------------------
The responses were:
Dear Rich,
This is probably totally useless, but we have quite a number of X
terminals, and PCs which sometimes act as X terminals. They all
work on the principle of sending an XDMCP broadcast, building up
a list of available hosts, allowing the user to pick one from the
list, and then presenting them with a login screen from such-and-such
a machine.
Now, for the unix end. The linux box upon which I type this is
running xdm. If I were sitting at a typical X terminal, and chose
this machine from the list, I'd get the standard xdm login window
(xlogin widget?). Assuming I logged in correctly, xdm would run
the .xsession script in my home directory, or some system-wide
default .xsession file. Now, looking at one of our alphas, I see
that dtlogin is running (/usr/dt/bin/dtlogin here) in daemon mode.
This does the same as xdm, only prettierly (interesting word, that!).
It's all, IMHO, more civilised than telnetting in and starting up
the xsession oneself, but it boils down to the same thing in the end.
Right, sorry if I've bored you, but one more thing. Make sure that
Xvision's hosts list includes the alpha. It's probably well hidden
in either a separate program, or many menus.
Hope you get it sorted. Also hope I haven't been patronising. :-)
Regards,
Wesley Darlington,
Dept. Applied Maths,
Queen's University of Belfast.
_______________________________________
Hi rich,
If you get the error 'Cannot obtain database information on this terminal',
Follow this advice from the Digital support people and change the
files /etc/auth/system/ttys, /etc/auth/system/devassign and /etc/securettys
as follows:
------
In the following, replace host, host.sub.domain and n.n.n.n by the
hostname, full domain name and IP address of the host(s) you are trying to
connect from.
Add lines like the following to /etc/auth/system/ttys :
host\:0:t_devname=host\:0:t_xdisplay:t_login_timeout#0:chkent:
Add lines like the following to /etc/auth/system/devassign :
host\:0:v_devs=host\:0,host.sub.domain\:0,n.n.n.n\:0:v_type=xdisplay:chkent:
Add lines like the following to /etc/securettys :
host.sub.domain:0
host:0
------
Elcana
Campinas,SP - Brazil
-----------------------------------------------
original question:
> Greetings,
> I am connecting to our DU4.0x systems from an NCD terminal by creating a
> Telnet session from the NCD to the DEC and then running the following script:
> on the DEC . (Wolfrm is the name of the NCD terminal)
> set DISPLAY WOLFRM:0
> export DISPLAY
> /usr/dt/bin/Xsession
>
> The Windows 95 system is running Xvision software and it has several options
for
> starting an Xsession. The above method and the others we have tried have not
> been successful. Any suggestions would be appreciated.
>
> Thanks for the help.
> rich
> rnfrank_at_llnl.gov
>
Received on Fri Apr 11 1997 - 00:43:00 NZST