Your message dated Sun, 27 Jun 2010 22:55:34 +0200
with message-id <[email protected]>
and subject line not a bug
has caused the Debian Bug report #411416,
regarding delivering kill signal from python to mplayer
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
411416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411416
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python
Version: 2.4.4-2
I'm witnessing inexplicable effect when trying to deliver SIGKILL from
a python script to running mplayer process.
The script:
#!/usr/bin/python
import subprocess
import os
import signal
import time
PATH_MPLAYER='/usr/bin/mplayer'
cmdList = [PATH_MPLAYER, '/home/woodmood/tmp/delme.wav']
# proc = subprocess.Popen (cmdList)
pid = os.spawnv (os.P_NOWAIT, PATH_MPLAYER, cmdList)
time.sleep (5)
# os.kill (proc.pid, signal.SIGTERM)
os.kill (pid, signal.SIGKILL)
os.wait()
What happens when run from Konsole is that mplayer dies, *without*
writing anything to the terminal and the script terminates and command
prompt reappers.
However, if I press any keys, nothing appears on the screen
(confiriming by enter executes a command though). This is most
probably an error in python because when I try running mplayer
manually and then sending it signal using:
$ kill -SIGKILL mplayer's_pid
mplayer dies stating 'Killed' and terminal stays alive as it should.
best regards,
Ales Kozumplik
--- End Message ---
--- Begin Message ---
not a bug (as explained in previous¹ mail)
[¹] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411416#10
--- End Message ---
