thanks a lot, Tim.
> -----Original Message-----
> From: owner-fvwm_at_hpc.uh.edu [mailto:owner-fvwm_at_hpc.uh.edu]On Behalf Of
> Tim Phipps
> esteffl_at_pbi.net wrote:
> > I thought that the fvwm crashed but then I checked 'ps -ef|grep fvwm'
and
> > I saw that all the fvwm processes are running (fvwm itself and few
modules).
>
> Since you can get to a shell you can send the USR1 signal to
> fvwm and it should restart.
where did you find this out? it really works, I just tried it, hopefully
it works when the fvwm disappears again.
> > my configuration:
> > fvwm 2.2.2
> > solaris
> > exceed (X server under windows NT)
> Exceed might have something to do with it. Try turning off any screen
> savers or running exceed in full screen mode
> (Exceed_menu/tools/configuration/screen_definintion/window_mode =
> single).
I already run exceed in fullscreen mode. and I have to run screensaver (we
have to lock the machine when we go away)
did anybody experience similar behaviour? is there any known reason for
fvwm to stop manage windows? it happens quite rarely and usually after
weekend.
erik
--
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 Tue Oct 26 1999 - 10:27:09 BST