[mythtv-users] mythcommflag stops early on a fast machine (maybe ?)

Michael T. Dean mtdean at thirdcontact.com
Thu Nov 27 13:02:42 UTC 2008

On 11/26/2008 10:42 PM, Christopher X. Candreva wrote:
> On Wed, 26 Nov 2008, Michael T. Dean wrote:
>> Most likely mythcommflag is segfaulting because of bad/unexpected data 
>> in the recording causing a segfault in some of the libav* code.
> Wouldn't that show up as an abnormal exit in the backend logs (as seen in 
> mythweb) ? The logs show it ended normally.
> If not, would the seqfault show up in mythjobqueue output, or should I look 
> someplace else ?

Nope.  TTBOMK, the separate mythcommflag job just dies, then the 
mythbackend process logs messages saying that the job is done.


More information about the mythtv-users mailing list