Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!grunwald@foobar.colorado.edu From: grunwald@foobar.colorado.edu (Dirk Grunwald) Newsgroups: comp.unix.ultrix Subject: Re: xcons murders the X server Message-ID: <12315@boulder.Colorado.EDU> Date: 3 Oct 89 05:22:48 GMT References: <4327@buengc.BU.EDU> <1880@bacchus.dec.com> Sender: news@boulder.Colorado.EDU Reply-To: grunwald@foobar.colorado.edu Organization: University of Colorado at Boulder Lines: 32 In-reply-to: klee@gilroy.pa.dec.com's message of 2 Oct 89 22:41:22 GMT In article <1880@bacchus.dec.com> klee@gilroy.pa.dec.com (Ken Lee) writes: Newsgroups: comp.unix.ultrix Date: 2 Oct 89 22:41:22 GMT Sender: news@decwrl.dec.com Organization: DEC Western Software Laboratory In article <4327@buengc.BU.EDU>, bph@buengc.BU.EDU (Blair P. Houghton) writes: > A few hours after starting up the xcons (by putting the proper line > in /etc/ttys and doing kill -HUP 1), the console-display's X server > (Xqdsg) locks up. Note that the xcons and xterm -L stuff will be removed from X11R4 by MIT. At best, it's kind of flakey. Try using xdm or dxsession instead. Ken Lee DEC Western Software Laboratory, Palo Alto, Calif. Internet: klee@decwrl.dec.com uucp: uunet!decwrl!klee ---- How does XDM solve the problem? It doesn't initiate a console-like window, it only prompts for passwords & starts your .xsession. dxsession, on the other hand, *does* capture console output; but w/o source, there's no way to see how this is done. Right now, I use all X11R3 tools except for dxsession, precisely because dxsession captures all console output. Kind of stiff cost, though. Dirk Grunwald -- Univ. of Colorado at Boulder (grunwald@foobar.colorado.edu)