elgordo123 suggested:
I replied:
Cecil requested:

Here is the drill... If you're using R5A12 or later:
1) As root remove /etc/cron.daily/mythtv-backend

2) From the main menu go to Utilities/Setup -> Setup -> General -> 7th screen
3) Check the box for "Automatically run mythfilldatabase"
4) Set "mythfilldatabase Path:" to /usr/bin/mythfilldatabase
5) (optional) Set "mythfilldatabase Arguments:" to --quiet (I didn't set up any logging)
6) Set the frequency, start and stop times to something reasonable. I picked a 6 hour stretch when I'm not normally watching it and it runs at a semi-random time during that window.

BTW - I've been doing this since shortly after upgrading to R5A12 with MythTV 0.17 and it's worked flawlessly. The only schedule feed problems I've had were due to external issues (My ISP's DNS failures, zap2it having problems, ...)

Will this work with other grabbers, as my mythfilldatabase doesn't work with my grabber.

Thanks

_________________
Girkers

I suspect so. I believe all it does is run whatever process you tell it to.

wow the forum is great I was about to post a question as to why mythweb gave me this error

Last mythfilldatabase run started on 2005-06-13 06:29 and ended on 2005-06-13 06:29. mythfilldatabase ran, but did not insert any new data into the Guide. This can indicate a potential grabber failure.
There's guide data until 2005-06-27 03:00 (14 days).

but I think I know why, guess i will know for sure tommorow

great program

The next release (when it is ready) doesn't have mythfilldatabase running as a cron job. You need to switch over to having MythTV run it at a random time. You've been warned.

As we get closer.... Another warning.

_________________
cesman

When the source is open, the possibilities are endless!

Last warning. If you plan to auto upgrade, you MUST do this...

How about detailed directions, how to disable cron job enable internal!

Craig

I enabled internal but not sure how to tell if the cron job is running or if it ever was.

It is posts like this that drive me batty. You are asking for help, yet your tone is rather sharp. You made a modification, yet you cannot undo the modification. Normally if you do something, you should have the knowledge to undo it. If you went from steps a - n, yet got messed up someway along the way, you should post exactly what you did. The contains of cron aren't carried over during an auto-upgrade. All one has to do to remove an entry in one's crontab is cron -e. Then comment or remove what you want...

_________________
cesman

When the source is open, the possibilities are endless!

Did not mean for the tone to be sharp just jotted a quick note, efficient but not polite I guess.

As for undoing things I could undo the internal database no problem as I did it and do keep notes on most changes i make. I just rebuilt my Myth box from ground up in one evening, a month long project my first time. I have never setup a cron job and do not know how, although I am sure a search of the forums would provide me with that info. I did not mean to offend you at all I just thought that it would be nice for noobs like myself to have a quick direction edit this file delete this command etc. Although again I must apologize because i see that earlier in this post are just such directions, I had not looked at previous pages. So for anyone else wondering what to do.
Here is the drill... If you're using R5A12 or later:
1) As root remove /etc/cron.daily/mythtv-backend
Code:
rm /etc/cron.daily/mythtv-backend

2) From the main menu go to Utilities/Setup -> Setup -> General -> 7th screen
3) Check the box for "Automatically run mythfilldatabase"
4) Set "mythfilldatabase Path:" to /usr/bin/mythfilldatabase
5) (optional) Set "mythfilldatabase Arguments:" to --quiet (I didn't set up any logging)
6) Set the frequency, start and stop times to something reasonable. I picked a 6 hour stretch when I'm not normally watching it and it runs at a semi-random time during that window.
Credit to TJC

Looking forward to the new release.

Craig

I have question about the auto mythfilldatabase function....

Does the $time parm passed to the "Set Wakeup Time Command" script by mythbackend at shutdown time take into account the next scheduled run time for mythfilldatabase?

In otherwords, will my system power up for the next scheduled automatic mythfilldatabase run, just like it currently does for scheduled recording?

If not, I'm considering an alternative of adding code to "Set Wakeup Time Command" script to generate a random time for next run of mythfilldatabase and if it were to occur before the passed $time value, pass it to nvram-wakeup. Of course, would also need code to detect the need to run mythfilldatabase on the next boot.