Mark Naumann <rysw20_at_email.mot.com> wrote:
}When fvwm does not exit, it goes into some runaway mode. The next time I
}login, my .xsession starts a new fvwm process. Now I have one runaway (from
}previous login) and this new fvwm process. If I don't manually kill the old
}process, it just sits there consuming CPU cycles (and upsets a lot of my
}colleagues!)
i also get this, but it isn't sporadic -- it happens all the time if i
don't explicitly quit fvwm. this is happening to everyone that i know
of using the copy of fvwm2 i compiled. most, myself included, have made
fvwm our session manager, thus eliminating the problem by forcing us to
quit fvwm before logging out. if not explicitly killed, the process
hangs around, and the load sits at a constant 1.0 until the process is
killed off. I'm using fvwm 2.0.41 under ultrix 4.3, osf/1 3.2, and irix
5.3.
--chris.
--
chris rode - crode_at_iastate.edu -- Help Room Consultant
http://www.public.iastate.edu/~crode/ -- 138 Durham Center, 294-1314
"why don't we just have a stupidity depeche mode, erasure, moby, new order,
tax? just tax the stupid people!" pet shop boys and recoil rock my world.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Mar 28 1996 - 10:48:55 GMT