[comp.sys.sgi] x-windows + startup

dsk@casbah.acns.nwu.edu (Daniel Katz) (04/25/91)

My .login contains:

        xinit -- /usr/bin/X11/Xsgi -pseudo
                                gamma 2.2
                                xclock -g 200x200+180+40 -bg blue -fg white -hd grey &
                                xbiff -g +30+220 &
                                makemap

to startup x-windows and upon exiting, reset the screen.

My .xinitrc contains as its last line:

twm

so that exiting twm exits x-windows.

My problem is that occasionally (increasingly) when x-windows finishes, the
standard light blue background comes back, with the various chests, but the
x-window windows don't close.  In this situtation, certain windows under
x-windows opened as SG windows, with the lightning bolt, not as x windows.

Can anyone explain what might be happening?

Thanks
-- 
Dan Katz                                                    1(708)491-8887
Dept. of Electrical Engineering                          +----------------
Northwestern University, Evanston, IL, 60208             |dsk@eecs.nwu.edu

ken@ag.msc.edu (Ken Chin-Purcell) (04/26/91)

Daniel Katz writes:
....My .login contains:
....
....        xinit -- /usr/bin/X11/Xsgi -pseudo
....              xclock -g 200x200+180+40 -bg blue -fg white -hd grey &
....              xbiff -g +30+220 &

I'll give this a stab...  Right now, X is layered on top of NeWS.
So when you log in, NeWS starts up (the blue background is a consequence
of this.)  Then your .login starts up the X server.  At this point
there is still a blue background (i.e. no X root window).

The familiar X root window appears only when twm starts up.  When you quit
twm, the X server is still alive!  You just lose the root window.

Don't panic, just take the extra step of logging out of NeWS.  This will
kill the root process of your session, which of course zaps everything.

You could be brutal and send a '/etc/killall news_server' after 
you quit twm.  The gentle user just exits twice, (1) X, (2) NeWS.

BTW, with IRIX 4.0 it looks like SGI will implement a 'normal'
X startup sequence (no need to hand start X with xinit, no more
NeWS lurking beneath your noble X windows). :)

-- 
--  Ken Chin-Purcell, Graphics, AHPCRC, Minnesota Supercomputer Ctr.
--  also known as ken@msc.edu and 612-626-8090

portuesi@tweezers.esd.sgi.com (Michael Portuesi) (04/27/91)

In article <3979@uc.msc.umn.edu>, ken@ag.msc.edu (Ken Chin-Purcell) writes:
|> BTW, with IRIX 4.0 it looks like SGI will implement a 'normal'
|> X startup sequence (no need to hand start X with xinit, no more
|> NeWS lurking beneath your noble X windows). :)

Well, actually NeWS sits on top of X windows in IRIX 3.x.  It serves as
an X window manager for X clients, and does its event handling ahead of
the X server.

m.

__
\/  Michael Portuesi   Silicon Graphics, Inc.   portuesi@sgi.com

paquin@kahua.esd.sgi.com (Tom Paquin) (05/04/91)

In article <1991Apr24.185317.18419@casbah.acns.nwu.edu>, dsk@casbah.acns.nwu.edu (Daniel Katz) writes:
|> My .login contains:
|> 
|>         xinit -- /usr/bin/X11/Xsgi -pseudo'

This is probably a bad idea.  Everytime you get a login shell,
.login tries to start an X server.  The default behavior in
3.3.2 is for an X server to be run at startup for you (depending
on chkconfig- see xstart(1), which goes away in 4.0).  Your
xinit may be attempting to start another server (which will 
block until the first server dies, then try to start).

		-Tom
*****
Opinions are mine, etc.