That's the method I used to set it up. I followed all of those instructions exactly, and it works for the rest of that day, but clears out after that.
I run mythfilldatabase at night, so I think that's the culprit. Not running mythdatabase, however, is obviously not an option. I could reduce its run frequency, but resetting my search rules once a week is only marginally less of a hassle than resetting them once a day.
You shouldn't have to reset the rules. If the schedule is correct when add a search rule it should be okay any other time the scheduler runs. The logs for mythfilldatabase and the master backend should have clues if something went wrong. Look for error messages and also check for the lines that say how many items where scheduled.
2005-03-04 06:41:59.496 Reschedule requested for id -1. 2005-03-04 06:42:05.502 Scheduled 378 items in 3.9 = 2.98 match + 0.88 place
If it had items before but then zero when mythfilldatabase runs, that would be a problem. Also, you can try running mythfilldatabase from the command line to see if that causes a problem.
So, was the schedule okay after you first set the rule? Is the schedule okay when you restart the master backend? When the schedule is blank, does running "mythbackend --resched" from another shell fix the problem? If this does happen when mythfilldatabase runs, is there show information in the Program Guide?
If it does seem to be related to having search rules, could you sent the output of:
$ mysql -u mythtv -pmythtv mythconverg mysql> select type,title,description from record where search=1\G
-- bjm
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
