"'John Kline' via weewx-user" <[email protected]> writes:
> Do I have it right that you are not interested in why the reporting > cycle is taking too long and spilling into the next archive cycle? I think the OP is pointing out that if a reporting cycle takes too long -- which could happen for lots of reasons, including database access bloat in new versions, loads other than weewx, etc. -- then weewx can end up starting a new reporting cycle when the other one has not finished, and this seems like a bug. It seems obvious (dangerous logic I know) that only one report should run at a time, and that if things are backed up doing every nth one is better than crashing. I would expect a mutex/etc. to guard against two reports at the same time. And agreed that for a healthy system one needs to address the overlength reports. But that's separable from reasonable behavior when they are too long. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/rmimrv2f6pr.fsf%40s1.lexort.com.
