Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!husc6!husc4!nakada From: nakada@husc4.HARVARD.EDU (Paul Nakada) Newsgroups: comp.windows.x Subject: Re: xterm and R3 Message-ID: <535@husc6.harvard.edu> Date: 31 Oct 88 22:19:30 GMT References: <178@umigw.MIAMI.EDU> Sender: news@husc6.harvard.edu Reply-To: nakada@husc4.UUCP (Paul Nakada) Organization: Harvard University Science Center, Cambridge MA Lines: 36 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 | __|