nanogui@linuxhacker.org

Thanks for the replies!

I found that flnx starts nano-X with the -p flag.  Removing that flag
in my local copy solved the problem.

Going to a different VC kill the server is only a solution if another
VC exists.  This is not necessarily the case with handhelds, set-top
boxes, etc.  I'm looking forward to the new version that will have a
way to stop a persistent server.

Regards,
Rob

------Original Message------
From: "Greg Haerr" <greg@censoft.com>
To: "Rob Martin" <rdmartin@mail.com>, <nanogui@linuxhacker.org>
Sent: August 30, 2000 3:55:08 PM GMT
Subject: Re: killing nano-X after app terminates


: How does one (manually, if necessary) cause nano-X to exit after the
: last application has exited?  Hitting ESC only works if an
application
: is running.

Nano-X will exit after the last connection unless the
-p option is given, or the window manager was running,
which Alex alluded to.  The Window manager could be
modified to exit when no more connections exist, and
then the server should exit as well.  As I mentioned, I'll
work on this and fix it for the next cut.

Regards,

Greg

----
Rob Martin
rdmartin@mail.com
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup