[mythtv-users] Randomizing startup times for mythfilldatabase from cron

[Adam Bodnar]

Has there been any thought as to retrofit the mythfilldatabase for .18
so that it uses the suggested time?

This way those of us that are going to wait on .19 can still not cause
Zap2it problems.

On 2/14/06, Ramon Redondo <malinon at gmail.com> wrote:
> On 2/13/06, Yeechang Lee <ylee at pobox.com> wrote:
> > Greg Estabrooks <greg at phaze.org> says:
> > > > So when is the best time to be running the cron job for retrieving
> > > > listings?
> > >
> > > Don't use a cronjob, use the built in ability for the backend to run
> > > mythfilldatabase itself. It will honour the suggested downlaod time
> > > from zap2it and allow them to spread their load.
> >
> > And, for those of us who are still holding off on upgrading to 0.19
> > for one reason or another and are still using crontab, do what I do,
> > based on the recommendation in Jarod Wilson's guide:
> >
> > ### Run mythfilldatabase every night randomly in a 4-hour block after
> 3:01am
> > 01 3 * * * sleep $(expr $RANDOM \% 14400) && mythfilldatabase >
> /var/log/mythtv/mythfilldatabase.log 2>&1
> >
> > I'm a little surprised, based on the discussions I see here, of the
> > number of people who apparently *weren't* doing something like this
> > already; go figure.
>
>
> I'm a little suprised at the number of people who are 'waiting for 0.19'
> before letting Myth schedule  their  database pulldowns.  It's been there
> since at _least_ 0.18.  Sure, the 'suggested time' won't be used, but they
> already support a random pull-down with a specified time range.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>