[ATrpms-users] mythcommflag and mythtranscode in mythtv-frontend, not mythtv-backend?

[Joe Votour]

<snip>
>
> Yes, but what about mythtranscode and mythcommflag? You initially
> suggested to move them to the backend, which seems wrong. Is the above
> list replacing those two, or is it in addition?
> --

Axel,

I thought you were asking about other programs, not mythtranscode and
mythcommflag.  I was just trying to list what the rationale for the other
programs was.

As for mythtranscode and mythcommflag, the MythTV wiki documents indicate
that they run on the frontend - but ever since I've had a dedicated
frontend and a dedicated backend, they've never run on the frontend.  (In
fact, that's why I made a dedicated backend, because mythcommflag was
killing my CPU on my combined machine while trying to watch HD.)

The documentation indicates that the default setting is to be to run
mythcommflag on the machine that created the recording.  However, you can
configure it to run on any machine through mythtv-setup.  The same appears
to be true for mythtranscode.

Given that, mythcommflag and mythtranscode clearly belong in both the
frontend and the backend (or maybe even another machine!), depending on
the user's configuration.  It might be simple like mine (dedicated FE and
dedicated BE), even simpler (combined FE/BE), or more complex (farm of
servers recording, which another farm doing commercial flagging and/or
transcoding).

Three possible solutions I see:
1. Make the RPMs for the frontend and the backend each contain
mythcommflag and mythtranscode
2. Make mythcommflag and mythtranscode into their own RPM, listed as a
dependency on both the frontend and the backend
3. Force users who want a dedicated backend to install the mythtv-frontend
RPM as well (which is the current setup).

Your thoughts?

-- Joe


___________________________________________________________
$0 Web Hosting with up to 200MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com