id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
7608	Slave backend disconnects	bob@…	cpinkham	"Since upgrading to mythtv 0.22-fixes from .21-fixes my slave backend disconnects after a couple of recordings. I have attached the log for the slave backend.  The backend is still running according to ps aux|grep myth:

Output from ps aux |grep myth|grep -v grep .. 
bob       1242  0.1  3.1 223016 32932 ?        Sl   Nov17   2:03 mythbackend
bob       4165  0.0  0.0   1772   480 ?        S    Oct27   0:00 sh -c /usr/local/bin/mythcommflag -j 35735 -V 3
bob       4166  0.0  2.5  84628 26364 ?        Sl   Oct27   0:00 /usr/local/bin/mythcommflag -j 35735 -V 3
bob       4897  0.0  0.0   1772   484 ?        S    00:59   0:00 sh -c /usr/local/bin/mythcommflag -j 36448 -V 3
bob       4898  0.0  2.5  84632 26796 ?        Sl   00:59   0:00 /usr/local/bin/mythcommflag -j 36448 -V 3
bob       5285  0.0  0.0   1772   484 ?        S    02:00   0:00 sh -c /usr/local/bin/mythbackend --generate-preview 0x0 --chanid 2048 --starttime 20091118020000 
bob       5286  0.0  2.5  85584 26868 ?        Sl   02:00   0:00 /usr/local/bin/mythbackend --generate-preview 0x0 --chanid 2048 --starttime 20091118020000
bob       6654  1.3 12.9 281532 134188 pts/0   SLl+ Nov10 155:13 mythfrontend
bob      21970  0.0  0.0   1772   480 ?        S    Nov14   0:00 sh -c /usr/local/bin/mythcommflag -j 36322 -V 3
bob      21971  0.0  2.3  84592 24828 ?        Sl   Nov14   0:00 /usr/local/bin/mythcommflag -j 36322 -V 3

The backend status page shows the slave backend mythcommflag with a status of starting at 12:59AM.  Every time the slave backend disconnects the list of processes is similar.  I tried asking on the mythtv-users mailing list but didn't get any response.  I never had a problem with .21-fixes, both compiled from svn.

"	defect	closed	minor	unknown	MythTV - General	unknown	medium	Fixed			0