Path: utzoo!attcan!uunet!van-bc!ubc-cs!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!ucbvax!ucdavis!csusac!unify!openlook!openlook-request From: smarks@Eng.Sun.COM (Stuart Marks) Newsgroups: comp.windows.open-look Subject: Re: Login support from within openlook Message-ID: Date: 7 Nov 90 18:47:32 GMT Lines: 33 karin@lia (Karin Meyer) writes: > b) Have windows up and running on a workstation, log in to a > window, which then automatically brings up the application. > Exiting the application would place the user back at the > login state. grp@unify.com (Greg Pasquariello) writes: | Unfortunately, to exit the session you will need to kill the | window manager. I do not know of a way to do this, other than | via a kill -9. You probably don't want to do a "kill -9" on the window manager. This will kill the window manager all right, but it won't restore things to a reasonable state. Among other things, the input focus will probably be left in limbo, and window borders won't be restored. Olwm will respond to SIGHUP, SIGINT, and SIGTERM by first restoring things to be reasonable state and then exiting. If you need to kill olwm, you should use one of these signals instead. You may not need to kill olwm at all, though. You could set up the default xdm session to have the session lifetime depend on your application. If you quit the application, the session will exit. You could also wire up an olwm root menu whose sole entry is "EXIT". This will limit the user's options to running the application or quitting, which seems close to what you want. s'marks Stuart W. Marks ARPA: smarks@eng.sun.com Windows & Graphics Software UUCP: sun!smarks Sun Microsystems, Inc.