Menu

#12 custom action causing zombie process

open
nobody
None
5
2002-11-10
2002-11-10
No

I've written a small shellscript (also tried it with a
native C application) which I used to launch several
programs with little delay and locking facility. So
this launcher can only be called once per 100msec.
(Workaround for another waimea bug - described in
another bug report)

This works "fine" for a single key press. But as soon
as I hold down the key for a few seconds I get a HUGE
amount of Zombie processes which can only be terminated
by killing waimea itself. - Causing the termination of
X... Relogin, etc... (Could write a workaround to
restart waimea as soon as 10 Zombie processes are
there, but that is totaly brain-damaged imho.)

This is what I have in my action file:

DEF ibmkeys {
{ /home/virus/.ibmkeys/ibmkeys stop } : KeyPress = F20,
{ /home/virus/.ibmkeys/ibmkeys play } : KeyPress = F21,
{ /home/virus/.ibmkeys/ibmkeys vol- } : KeyPress = F22,
{ /home/virus/.ibmkeys/ibmkeys vol+ } : KeyPress = F23,
{ /home/virus/.ibmkeys/ibmkeys prev } : KeyPress = F24,
{ /home/virus/.ibmkeys/ibmkeys next } : KeyPress = F25,
{ /home/virus/.ibmkeys/ibmkeys mute } : KeyPress = F26
}

"ibmkeys" is really nothing special. It does nothing
but calling xmms and setmixer. Even a script which
simply calls a single "sleep 1" will result in such
Zombie desaster.

ps.
The F20-F26 are the mapped multimedia keys from my IBM
RapidAcess II Keyboard.

I hope I could help pointing out another waimea bug (?)

Discussion


Log in to post a comment.

Auth0 Logo