mythtv at cvs
Nov 3, 2009, 3:53 PM
Post #10 of 20
(325 views)
Permalink
|
|
Re: Ticket #7315: mythtranscode doesnt die after lossless transcoding to cut out ads
[In reply to]
|
|
#7315: mythtranscode doesnt die after lossless transcoding to cut out ads
------------------------------------+---------------------------------------
Reporter: oobe.trouble@… | Owner: ijr
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: head
Severity: medium | Mlocked: 0
------------------------------------+---------------------------------------
Comment(by robwebb5@…):
I see this issue too (release-0.22-fixes 22714) and previous 0.22-fixes
versions.
At a guess, mythtv is launching a shell to launch the transcode command -
while the transcode is running the following jobs are active:
{{{
rob[at]mediapc:~$ ps -Af | grep trans
mythtv 13708 3209 0 23:37 ? 00:00:00 sh -c
/usr/bin/mythtranscode -j 10 -V 3 -p autodetect -l
mythtv 13709 13708 55 23:37 ? 00:00:12 /usr/bin/mythtranscode -j
10 -V 3 -p autodetect -l
}}}
After the transcode job is finished you are left with:
{{{
rob[at]mediapc:~$ ps -Af | grep trans
mythtv 13726 1 0 23:39 ? 00:00:00 /usr/bin/mythtranscode -j
10 -V 3 -p autodetect -l
}}}
Note that the parent process of the transcode job has changed from 13708
(the shell that mythtv launched) to 1, which would indicate the parent
process has been killed.
Leaping into wild conjecture here, mythtv launches the shell job to
perform the transcode job and keeps track of the pid that it spawned. When
the transcode job is done mythtv reaps that pid, '''but''' it is reaping
the pid of the shell, not the pid of the transcode command that the shell
spawned.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/7315#comment:9>
MythTV <http://www.mythtv.org/>
MythTV
_______________________________________________
mythtv-commits mailing list
mythtv-commits[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits
|
