[drupal-docs] cron jobs in the install text
Anisa
mystavash at animecards.org
Wed Mar 16 04:08:07 UTC 2005
One thought. If your search yeilds no results, then perhaps a
suggestion, if they are just beginning the site, that they need to set
up a cron job? (still no clue how to do this, please point me to a
forum thing if you know of one). Probably want to make this message
limited to administers, and perhaps let it be disable-able.
Anisa.
Morbus Iff wrote:
>> Two years (and one day ago today), I thought about this as well [1].
>> Up to this point the only message I ever found in the logs is "last
>> cron not completed" (or so) which is almost useless. We should focus
>> on more usefull error messages here, for example "The site listed in
>> the aggregator (http://example.com/rss) was unreachable"
>
>
> Well, that's still a bit of a problem. How can you write a warning to
> the log that cron ISN'T running, when the only time that warning would
> be legitimately written is if cron WAS running? (ie. how can you time
> a warning message that a timed process isn't timed?)
>
> The only thing I can think of is contextual only
> clues. For instance, regarding the search module:
>
> * search.module checks for an index, or the outdatedness of one.
> * on the next search (the untimed trigger), the search.module spits
> a watchdog that the index hasn't been updated in XX days. On a
> heavy site with lots and lots of searches, this would surely
> spam the watchdog (which may be a good thing, actually).
>
> But that doesn't solve any of the other timed examples that don't have
> an easily determined trigger.
>
More information about the drupal-docs
mailing list