Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!spool.mu.edu!uunet!munnari.oz.au!bunyip.cc.uq.oz.au!griffin!gucis!anthony
From: anthony@gucis.sct.gu.edu.au (Anthony Thyssen)
Newsgroups: comp.windows.x
Subject: Re: Xterm console window problems
Message-ID: <1991Jun4.034753.4623@gucis.sct.gu.edu.au>
Date: 4 Jun 91 03:47:53 GMT
References: <1991Jun3.125642.11785@vaxa.strath.ac.uk>
Organization: Griffith University
Lines: 39

craa79@vaxa.strath.ac.uk (Bruce Rodger.) writes:
>Problem:
>rlogin to a sun (3/80, running sunos 4.0.3), and start up an Xterm console
>window.
>The normal console (NOT running a window system) gets grabbed - if a user
>is logged onto the console, the user who started the xterm gets BOTH sessions
>connected to the xterm.
>If the Xterm is now killed, control is NOT returned to the console - the only
>solution is to reboot......
>Any solutions ?

>Bruce.

A simular problem exists when using Xterminals or X servers that query
on a remote machine for a XDM login. If the session starts a console (-C flag)
the previous console on the machine (either the real console or another
persons xterm -C console) is lost, as there can only ever be one console right!

My solution in installing X is to give the user (in the default Xsesson
file of xdm ( I changed startx script to also use the) ) a console
ONLY if he is running on the machine with the server (local)
EG:-

cd                              # go home!
HOST=`/bin/hostname`
case "$DISPLAY" in              # fix any display problems
  unix:0.0|unix:0|:0.0|:0|'')     DISPLAY="$HOST:0.0" ;;
esac

< resource stuff and window manager start deleted >

if [ "$HOST:0.0" = $DISPLAY ]; then
  xterm -g 80x8+5+5 -T "Console" -n "Console" -C &   # console
fi

< the rest of the setup >

xlogout -g -5-5   # the logout button
xclosedown        # clean up nicely first