Background: We've got a bunch of desktops running Solaris 2.6 and fvwm
2.0.45. Our users login with openwindows, and fvwm is started from user's
.xinitrc files. These desktops frequently hang, with dtlogin dying and
leaving an XSun process in bad shape. Restarting dtlogin without
killing the XSun will freeze the desktop to require a cold reboot.
I'm preparing to upgrade to fvwm 2.2.4 to see if this helps.
I'm puzzling over the section 2.2 of the dtwm FAQ that says:
Finally you have to quit with
/usr/dt/bin/dtaction ExitSession (or whatever your path is for dtaction)
I'm wondering:
a) does this even *apply* if I'm starting with openwindows instead of dtwm?
b) if it applies, what's the exact syntax to make it work? I'm trying
variations
of this in my .fvwm2rc without success:
AddToMenu FvwmCommands "Fvwm Commands" Title
+ "Exit Fvwm" /usr/dt/bin/dtaction
ExitSession
c) is there anything else we should be doing?
d) Is there any advantage to starting from dtwm instead of openwindows?
Has anyone had this problem and did you find a fix?
Also, is there a good "howto" or intro out there? I'm a bit of an X/desktop
newbie - I've been a unix sysadmin for quite a while but most of my Solaris
admin experience is on headless servers.
Thanks for any clues!
--
Elizabeth Schwartz 781-262-6565
Unix System Administrator eschwart_at_genuity.net
Genuity, Inc
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Dec 18 2000 - 20:53:12 GMT