Solaris

Well, my first post... thanks in advance! Can applications be notified of the X Window close (with "X" button) so the signal handler can run a cleanup process method?

About the app: built with GNU C/C++ on Solaris 10, with WxWidgets. It is launched by a shell script as a background task. The app becomes 'orphaned', a child of init (i think), because of fork/exec code...

The app acts as a controller, launching other apps, etc... We track the number of active users, by modifying a value in shared memory. On a normal entry and exit we modify the value...

Problem scenario: When you click the "X" on the X terminal window that launched the controller app, the controller app and everything it launched is killed... but it doesn't look like the signal handler is being notified of an event... Should i be getting a SIGHUP or other signal? something special from the window manager?

If I type 'exit' in the controlling X terminal, then the logout kills the interactive shell but the X Window remains open... processes running still...

would love code snippets... thanks, Jim

The process receives an XEvent, not a signal, and it's shut down by the event handler code in something like XtAppMainLoop().

thank you achenle, sounds exactly right... after playing with wxApp's OnExit, OnFatalException and others (app is built on wxWidgets)... no success getting an event so the app can clean up...

does anyone have a simple example of a wxWidget or X application that can detect the launching x terminal's death? If so, then I can fit that into the wxWidget app...

Before I started playing with the wxApp methods I was getting a message that may provide more clues. It's at the bottom.

thanks again for your help!! Jim


Trapped stdout and stderr when killing the X terminal that launches the wxWidgets app (hitting the 'X' window mgmt button):

X connection to localhost:11.0 host broken (explicit kill or server shutdown)
Gdk-ERROR **: X connection to localhost:11.0 broken (explicit kill or server shutdown).