Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!decwrl!ucbvax!hplabs!otter!hpcpbla!tim
From: tim@hpcpbla.HP.COM (Tim Phipps)
Newsgroups: comp.sys.hp
Subject: Re: running X from init
Message-ID: <660005@hpcpbla.HP.COM>
Date: 20 Dec 89 09:24:49 GMT
References: <1541@gwusun.gwu.edu>
Organization: HP Computer Peripherals Bristol, UK
Lines: 24

> and be _sure_ which tty the xterm will end up on.

This inittab results in the login terminal running on ttyq0 and kills the
server when the window dies.

X:2:respawn:env PATH=/bin:/usr/bin/X11:/usr/bin xinit sh -c "xinitcolormap -f /usr/lib/X11/cmap.8.primary; exec hpterm -fg white -bg black =+200+150 -n Login -L ttyq0" -- -co /usr/lib/X11/rgb.big :0 #XWindows

/etc/ttytype can have an entry for ttyq0 to set the TERM variable
automatically.

I used to use the following for a while:

XX:2:respawn:/usr/bin/X11/X :0                                  #XServer
XC:2:respawn:/usr/bin/X11/hpterm -display local:0.0 -L ttyq0    #XClient

This does not kill the server when you quit the login window
but unless you kill all clients off before exiting the login window
the server will not reset and you may inherit someone else's resources if
they are stored in the server!  Besides that I only exit X when it gets
too big (not a memory leak just too many windows) and then I want to kill
it anyway.

Merry Christmas
Tim.