From: Daniel Clar (Daniel.Clar@supelec.fr)
Date: Mon May 06 2002 - 06:10:20 EDT
The original posting was :
> Hello Managers,
>
> I'm not sure that it's a TRU64 Unix problem but it should be.
>
> My workstation is an OpenVMS workstation. At login time, I have some
> tasks in the automatic startup menu and some of them are opening DECterm
> windows in wich there are automatic rlogin commands on Tru64 Unix
> computers.
>
> I've always got problems with some of them following the Tru64 Unix
> version : after a fix number of seconds the Decterm is closed even if I
> was typing some characters and the process running is stopped. Then I
> was able to start again the same process from the Session Manager and
> the window never closed, so it seems that it's not an autologout time
> problem.
>
> Now all my Unix systems are running 5.1A and for all the systems but one
> the window is closed after some 90 seconds.
>
> The running shell is tcsh. The .login and .cshrc files on the user
> account are the same.
>
> Some ideas about this strange behaviour ?
Thank you to Selden E Ball Jr <SEB@LNS62.LNS.CORNELL.EDU> and I join the
full answer.
Daniel
-----------------------------
Check to make sure you don't have an "idle job killer" running
on the VMS sytesm. They are sometimes confused about how
to handle DECwindows.
I've never seen the problem you report, but you might consder a
different login method. Specifically, use rsh to run dtterm (or dxterm)
on the Tru64 systems, so that the Tru64 terminal emulator opens
a window on your VMS desktop. As a result, you are using a terminal
emulator that is running native on the remote Unix system rather
than using rsh within a VMS DECterm window.
This avoids many potential terminal emulator incompatibilities.
I usually use dxterm, since it is almost identical to the VMS DECterm.
I use the subroutines below within my auto-login script to open either
a DXterm or a DTterm window on the current X display screen.
The DCL subroutines are called with p1 set to be the remote host name.
e.g.
$ call rlg_dxterm host.computer.domain
They are spawned from a terminal window that is "never" logged out.
You'll have to change how "d1" (the local display's tcp/ip domain name)
is determined if you don't use Multinet.
$!=====================================================
$! Routine to rsh to remote unix and open DXterm window there to here
$rlg_dxterm: subroutine
$ wn = p1
$ def/user sys$output nl:
$ sho disp/sym
$ d1 = "''decw$display_node'"
$ if d1 .eqs. "0" then d1 = "''f$trnlnm(""MULTINET_HOST_NAME"")'"
$ d2 = "''decw$display_server'"
$ d3 = "''decw$display_screen'"
$ spawn/nowait/input=nl: -
rsh 'p1' "/usr/bin/X11/dxterm -display ''d1':''d2'.''d3' -iconic -xrm
""*iconName:''wn'"" -
-xrm ""*title:''wn'"" "
$ exit
$ endsubroutine
$!=====================================================
$!=====================================================
$! Routine to rsh to remote unix and open DTterm window there to here
$rlg_dtterm: subroutine
$ def/user sys$output nl:
$ sho disp/sym
$ d1 = "''decw$display_node'"
$ if d1 .eqs. "0" then d1 = "''f$trnlnm(""MULTINET_HOST_NAME"")'"
$ d2 = "''decw$display_server'"
$ d3 = "''decw$display_screen'"
$ spawn/nowait/input=nl: -
rsh 'p1' "/usr/dt/bin/dtterm -display ''d1':''d2'.''d3' -fn -dt-interface
-132 -ls -
-geometry 132x24 -iconic -ti vt220 -title ''p1' -name ''p1'"
$ exit
$ endsubroutine
$!=====================================================
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:40 EDT