We've been using the fvwm-1.24r for years with the following patch
to prevent clean-up problems when users log out. The problem was
sometimes users start things from their window manager menus which
are not intended to be daemons, but also do not launch any windows,
or the windows do not respond to the right signals to clean up when
fvwm2 exits. At the very least, we frequently were left with bogus
processes still running, and in the worst cases, the X greeter would
not restart. Maybe someone else understands this better, but simply
having the window manager try to clean up all its child processes
when it exits (not restarts) has worked quite well:
diff -ru fvwm-snap-20010916/fvwm/fvwm.c fvwm-2.5.0-cfht/fvwm/fvwm.c
--- fvwm-snap-20010916/fvwm/fvwm.c Fri Sep 14 01:00:07 2001
+++ fvwm-2.5.0-cfht/fvwm/fvwm.c Tue Sep 18 19:55:12 2001
@@ -1675,6 +1675,17 @@
*/
ClosePipes();
+ /* Any processes which FVWM started should also exit now, if they are
+ * still running in the same process group. Any program that wants to
+ * continue running after the user's window manager session is gone
+ * should create its own process group.
+ */
+ signal(SIGHUP, SIG_IGN);
+ signal(SIGTERM, SIG_IGN);
+ kill(0, SIGHUP);
+ sleep(4);
+ kill(0, SIGTERM);
+
exit(0);
}
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
