Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!olivea!apple!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: smarks@eng.sun.COM (Stuart Marks)
Newsgroups: comp.windows.x
Subject: Re: Exiting olwm
Message-ID: <9101230238.AA00713@trantor.Eng.Sun.COM>
Date: 23 Jan 91 02:38:07 GMT
References: <9101180039.AA05398@sequoia.cray.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 29


foster@sequoia.cray.com (Paul Foster) writes:
    How do you set up .xinitrc so that when you use the WMEXIT 
    property of olwm, all your windows will not be killed off?
    When I use the WMEXIT property to exit olwm, all my windows
    disappear and I am logged back out the console display.

The xinit program waits for the .xinitrc script to exit.  In your example,
quitting olwm causes the script to exit, which causes xinit to take down
the server.  If you want you session to outlive olwm, just put something
else in .xinitrc so that the script waits around for it instead of for
olwm.  For example:
    
    xrdb .Xdefaults
    eval `svenv -env`
    olwm -3 &
    $HOME/.openwin-init
    xterm -C -g 80x8 -name console

Note:  there is no '&' after the xterm console invocation.  This causes the
script to wait around until you exit the console xterm.  If you put this
into .xinitrc, you can kill and restart window managers pretty much with
impunity.

s'marks

Stuart W. Marks			ARPA: smarks@eng.sun.com
Windows & Graphics Software	UUCP: sun!smarks
Sun Microsystems, Inc.