Up: SGI graphics Frequently Asked Questions (FAQ)
Next: -39- Why doesn't the window manager's "Log Out" routine work in IRIX 4.0.5?
Previous: -37- How can I recover from a failed window manager customization attempt?
Subject: -38- Why is an extra 4Dwm burning CPU in IRIX 4.0.x?
Date: 07 May 1993 00:00:01 EST
This multiple window manager problem is usually triggered by the
"kill" feedback of the window manager when a user logs out. The
workaround for the problem is to remove the "kill" feedback.
The "kill" feedback is controlled by the resource "showFeedback."
For 4Dwm, this resource is defined in /usr/lib/X11/app-defaults/4DWm
as:
*showFeedback: behavior restart quit kill
Modify the resource to read:
*showFeedback: behavior restart quit
For mwm, set a "showFeedback" resource that does not include the
"kill" feedback in /usr/lib/X11/app-defaults/Mwm. A sample setting
is:
Mwm*showFeedback: move placement resize behavior restart quit
Up: SGI graphics Frequently Asked Questions (FAQ)
Next: -39- Why doesn't the window manager's "Log Out" routine work in IRIX 4.0.5?
Previous: -37- How can I recover from a failed window manager customization attempt?