> I'm running a combo frontend/backend on a very low-end server
> (p2/350MHz) and the commercial flagging takes a long time to do its
> thing.  I recently set up another machine with a lot more power (and
> noise -- so it's not going to be moving anywhere!) as a frontend.  When
> I try to do the commercial flagging either through mythfrontend or have
> the fe/be set up to do it on this other box it just does not seem to
> run.  I ran mythcommflag -f /path/to/file.nuv and it worked just fine.
> Any suggestions where to look to see why it's not working either
> automatically or manually?

The frontend program does not do commercial flagging.  It does not run
a JobQueue thread to process jobs in the queue.  When you tell Myth to
flag a program, it queues up a commercial flagging job which is run by
the JobQueue.  With current CVS (and with v0.17 which will be released
in the near future), the best way to accomplish what you are looking to
do is this:

* On the master (low-end) backend:
        - go into the master backend setup program to the jobqueue page
          and turn OFF the checkbox that says "Allow Commercial Detection jobs".
          This will stop commercial flagging jobs from running on your
          main slower backend.
        - make sure that "Run Jobs only on original recording host" is turned
          OFF so that new jobs are allowed to run anywhere.
        - restart mythbackend since it only reads this setting when it starts 
up.

* On the faster machine that you want to run flagging on do this:
        - go to the fast machine and run the backend setup program and go to
          the same JobQueue page you went to before and make sure that
          "Allow Commercial Detection jobs" is turned ON for this machine.
          This will allow commercial flagging jobs to run on this machine.
        - Run mythjobqueue.  The mythjobqueue executable looks at the
          JobQueue and runs jobs the same way that a full copy of mythbackend
          runs jobs, but it's much slimmer than running the full mythbackend.
          You want to leave mythjobqueue running so that it will pick up any
          new commercial flagging jobs that are added to the queue, otherwise
          the jobs will back up in the queue and your programs won't be flagged
          until you run mythjobqueue the next time.

-- 

Chris

_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to