I'm seeing a very bizarre behavior on my Debian GNU/Linux box (3.0).
I'm using the official packaged version of fvwm from unstable
(2.4.10-2). I had this same problem with the fvwm from testing (2.4.8)
so I upgraded, but upgrading didn't help.
I'm sure that this has not always behaved this way, but I suppose I
might not have noticed it for a while; I don't often look at my complete
process list. I haven't modified my .fvwmrc or anything in months.
The issue is that any process I start either from fvwm directly or from
FvwmButtons will go <defunct> after I exit it. It stays defunct
forever, with a parent of the fvwm process, until I restart fvwm.
For example:
# ps -aef | grep defunct
psmith 26363 26244 0 10:22 ? 00:00:00 [FvwmButtons <defunct>]
psmith 26368 26244 0 10:22 ? 00:00:00 [rterm <defunct>]
psmith 26572 26244 0 10:32 ? 00:00:00 [rxvt <defunct>]
psmith 26713 26244 0 10:37 ? 00:00:00 [rterm <defunct>]
psmith 26718 26244 0 10:37 ? 00:00:00 [rterm <defunct>]
psmith 26765 26244 0 10:44 ? 00:00:00 [rterm <defunct>]
# ps -aef | grep 26244
psmith 26244 1 0 10:22 ? 00:00:00 /usr/bin/fvwm -d :0.0 -s
-clientId 11c020967f000098873609811110258690033 -restore
/home/psmith/.fvwm/.fs-restart-lemming:0.0
...
The FvwmButtons above is because I killed the old one and restarted the
module, to see if changing my FvwmButtons commands like "Exec rxvt ..."
to "Exec exec rxvt ..." would help but it didn't.
I don't get it: is there some kind of known issue with fvwm where it's
not waiting for children? Or, maybe this is an issue with libc in
Debian or something like that?
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
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]
