[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::excursion

Title:note 3 has pointer to current kit
Notice:note 3 has pointer to current kit
Moderator:PEACHS::GHEFF
Created:Wed May 29 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3301
Total number of notes:14905

3278.0. "Killing a disconnected DXterm brings down excursion server" by NNTPD::"[email protected]" (Shayne Andreasend) Tue Apr 29 1997 03:25

Hi team,
With Excursion 3.0 (PW32 CD) and NT4,
If you run DXterms from two hosts (VMS) and one host
dies, the DXterm goes blank and does not disappear. If you then attempt
to kill it with the NT4 task manager, the excursion server and 
your other DXterms die.

The customer tells me this is new in eXcursion 3.0. 
2.1 was apparently OK in that if one of the hosts went away
the relevant DXterm will go away by itself leaving the
sessions from other hosts intact.

Has anybody else noticed this? Would it be covered in ECO1?

Thanks,

Shayne Andreasend
Sydney Customer Support Centre
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
3278.1PEACHS::GHEFFDo you feel like swimming?Tue Apr 29 1997 09:3112
    The issue with windows going blank and not closing is pretty new with
    3.0 and is reportedly resolved in the upcoming ECO.
    
    If you kill an eXcursion window with the task manager, you are killing
    the X server.  That's what I'd expect to see.  The X server controls
    all the windows, they are not separate NT processes.  It's kind of like
    having Netscape Navigator browser windows open, if you kill one of them
    with the task manager, all the others close too, because they're all
    being controlled by the same netscape.exe process.
    
    
    #Gary
3278.2Killing dxtermsNNTPD::"[email protected]"Shayne AndreasendTue Apr 29 1997 20:3617
Gary,
Thanks for confirming that window closure is an issue with version 3.0 -
I will look forward to seeing ECO 1. Do you know when this will
be available?

Regarding the use of the NT task manager to kill a window, if you
have three dxterms from the same host, you can use the task manager to
kill just one - try it. The other two dxterms and the session manager
remain intact. If you have dxterms from two hosts running, you
can still kill one of them and then press cancel when the message 
comes that a process (presumably the xserver) cannot respond
to the "end task" command. The remaining dxterms are still intact.
The problem I have seen is that if one of the dxterms is disconnected
from its host, then killing that process kills the xserver.

Thanks, Shayne
[Posted by WWW Notes gateway]
3278.3PEACHS::GHEFFDo you feel like swimming?Wed Apr 30 1997 10:2512
    Blink. Blink.  You're absolutely right about the task manager, I stand 
    corrected.
    
    Now I'm questioning whether or not it was always that way and I've just
    lost my memory, or if earlier versions really were as I described.
    (I've been supporting eXcursion since 1.0 and sometimes these things
    run together.)
    
    My wife teases me all the time about my memory loss.  Maybe she has a
    point. :-}
    
    #Gary
3278.4VMSNET::S_VORESmile - Mickey's Watching!Tue May 06 1997 19:525
    of course, the other end (VMS or UNIX) may or may not realize that
    you've killed sessions and the process on that remote system may or may
    not go away - and eXcursion has no control there.