5,838
edits
Category:Cumulus MX: Difference between revisions
m
→MX End of Day Process
m (Paste) |
|||
| Line 763: | Line 763: | ||
= MX End of Day Process = | = MX End of Day Process = | ||
I have added this section, because this process has given me some headaches. If you write custom SQL, or have a template being processed at end of day, then what I find strange is that web tags related to system date report the new date, but other web tags report weather derivatives from the old day. Put another way, the date changes at start of rollover, but the weather web tags change at end of rollover. However, it is not quite as simple as that, the month and year are reset after any Custom SQL is run (so that SQL can use monthly and yearly web tags related to previous day), but before the extra files are processed (so they cannot use monthly web tags at end of month, nor yearly web tags at end of year). See why I found it hard to digest, and why I wanted to write it here to make it easier for others. | |||
Mark Crossley says the MX day reset does this... | Mark Crossley says the MX day reset does this... | ||
| Line 782: | Line 783: | ||
Process Extra EOD files | Process Extra EOD files | ||
</tt> | </tt> | ||
But independent of that the normal processing | But independent of above EOD thread that occurs on the rollover hour, the '''normal interval''' and '''hourly processes''' thread is seeking to run at same time, whether that happens at same time depends on processing capability and whether it can process multiple threads. | ||
What happens depends on your settings, and if your FTP interval is synchronised with the logging interval | What actually happens in above list depends on your settings, and if your FTP interval is synchronised with the logging interval. | ||
= SPECIAL CONSIDERATIONS - Text by Steve Loft = | = SPECIAL CONSIDERATIONS - Text by Steve Loft = | ||