angel@umigw.MIAMI.EDU (angel li) (11/01/88)
I have build R3 on a Vaxstation 3200, 8 planes GPX color, Ultrix 2.3, and have the server running and the clients running. A major inconvenience with this release is that whenever an xterm window goes away, the entire session gets logged out. This gets old quickly. Has anyone seen this problem? Another problem seems to be with xdm. After logging off the main xterm window, xdm starts up another X server when another server is already running. I ran xdm with "-debug 99" and could not see why this was happening. -- Angel Li University of Miami/RSMAS Internet: angel@flipper.miami.edu UUCP: ncar!umigw!angel
nakada@husc4.HARVARD.EDU (Paul Nakada) (11/01/88)
In article <178@umigw.MIAMI.EDU> angel@umigw (angel li) writes: :I have build R3 on a Vaxstation 3200, 8 planes GPX color, Ultrix 2.3, :and have the server running and the clients running. A major inconvenience :with this release is that whenever an xterm window goes away, the entire session :gets logged out. This gets old quickly. Has anyone seen this problem? : :Another problem seems to be with xdm. After logging off the main xterm :window, xdm starts up another X server when another server is already running. :I ran xdm with "-debug 99" and could not see why this was happening. : : :-- :Angel Li :University of Miami/RSMAS : :Internet: angel@flipper.miami.edu UUCP: ncar!umigw!angel yes i have also experienced this phenomena... Actually i think it's doing more than just logging out your session. Check out your syslog to see if it "reinitialized" Ultrix. I assume that this is some sort of warm boot sequence, since it kills all logins. I too am running Ultrix 2.3 on a Microvax II with a monochrome display i also had the identical problem with xdm. btw. before it starts the second X, it kills all current logins.... btw. this is not a good thing when 7 people get nuked without any notice.. my bad... can anyone please help??! i think it might be something with XtFree or something like that... that's where xterm goes away... -paul nakada __ | Paul Nakada '89 #8-) | North House | nakada@husc4.HARVARD.EDU Harvard College | seismo>!harvard!husc4!nakada.UUCP Cambridge, MA 02138 | rutgers/ nakada@husc4.BITNET 617/498-6255 || 6264 | __|
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/01/88)
We think we're on the verge of figuring out why some exiting xterms cause Ultrix 2.3 to reinitialize the system (although we can't reproduce this under Ultrix 3.0 FT2). Hopefully later today ...
jim@EXPO.LCS.MIT.EDU (Jim Fulton) (11/02/88)
The problem is caused by a feature in Ultrix 2.* in which killpg(-1,SIGHUP) causes the system to reinitialize (which has since been fixed). A patch for xterm to fix its shutdown logic will be posted before the end of the day. Jim
yba@arrow.bellcore.com (Mark Levine) (11/02/88)
In article <178@umigw.MIAMI.EDU> angel@umigw (angel li) writes: >I have build R3 on a Vaxstation 3200, 8 planes GPX color, Ultrix 2.3, >and have the server running and the clients running. A major inconvenience >with this release is that whenever an xterm window goes away, the entire session >gets logged out. This gets old quickly. Has anyone seen this problem? > >Another problem seems to be with xdm. After logging off the main xterm >window, xdm starts up another X server when another server is already running. >I ran xdm with "-debug 99" and could not see why this was happening. [This is a second follow-up from me; I will try and cancel the first] I have seen this problem also under Ultrix 2.3 on a Vaxstation II/GPX; when an xterm exits, it seems to propagate a fatal signal all the way back to the init process. I run two servers on my vax, Xqdss and Xplx -- an xterm exiting on either kills both servers! Other clients do not exhibit this behavior, so I am going to stare at xterm. Other opinions, experiences and especially fixes solicited! Eleazor bar Shimon, once and future Carolingian yba@sabre.bellcore.com
yba@SABRE.BELLCORE.COM (11/02/88)
The problem is caused by a feature in Ultrix 2.* in which killpg(-1,SIGHUP) causes the system to reinitialize (which has since been fixed). A patch for xterm to fix its shutdown logic will be posted before the end of the day. Jim Thanks. I figured it would work if I could get 3.0, but they told me the real stuff will ship by the time the paperwork was done. Does "posted" mean to comp.windows,x or as a FIX from expo? Been so long since I sent for fixes I can't recall the address -- is it going to remain active?