[mythtv] Ticket #3062: Freebsd compatibility patches

usleepless at gmail.com usleepless at gmail.com
Thu Feb 8 23:32:48 UTC 2007


On 2/8/07, usleepless at gmail.com <usleepless at gmail.com> wrote:
> List,
> update on the sock.lock:
> my 0.18-fixes was already running without the readReadyLock. i removed
> sock.lock() as well, rebuild, reinstalled, restarted.
> started up first client on fbsd6.1, watching livetv. started up 2nd
> client on xbox, watched livetv. programmed a recording, and went back
> to livetv.
> 3 tuners running, 2 clients watching. works fine.

so, now it is 23.00 ( i removed the sock.lock around 16.00 ). out of
the blue, a frontend displayed "could not connect to backend" while
playing a recording. this never happened before. 2 clients were
watching, 2 commflaggers were running. i restarted it, but i think
this proves sock.lock is indeed necessary.

i tested further on the amd64-fbsd-mythtv-0.20 machine, and
reintroduced sock.lock() but now in MainServer::readyRead


this works for the amd64-fbsd-mythtv-0.20 machine. i applied the same
patch to my 0.18-fixes server, will have to wait a couple of days to
be sure.



More information about the mythtv-dev mailing list