5,838
edits
Dayfile.txt: Difference between revisions
m
→How you can use the daily log
(→How you can use the daily log: added new section "Populating a database table") |
|||
| Line 19: | Line 19: | ||
* Back ups of all the log files mentioned here (not all the log files) including dayfile.txt are copied to the 'cumulus\backup' folder, the last 8 only are retained. | * Back ups of all the log files mentioned here (not all the log files) including dayfile.txt are copied to the 'cumulus\backup' folder, the last 8 only are retained. | ||
== How you can use the daily log == | == How you can use the daily log == | ||
* If you want to run scripts that use the daily log, it is best if you take a copy first, you can ask Cumulus 1 to take a copy | * If you want to run scripts that use the daily log, it is best if you take a copy first, you can ask Cumulus 1 to take a copy after each update by using the '''Daily''' box in the bottom left of the ''Sites/Options'' frame within the ''Internet'' options screen from the '''Configuration''' menu; that will safely take a copy of 'dayfile.txt' after it is updated. This has the advantage it happens even if Cumulus has been stopped and restarted and rollover is happening during catch-up and so not at usual rollover time according to the computer clock. See Cumulus 1 '''Help''' for information on using this feature, I add a redirection ">daily_batch.log" in the parameter box alongside so that any output from running the command file I specify in the main box is sent to a log file overwritten in each run; this enables me to see the reason for any failure. | ||
* Cumulus MX has option to list files to be transferred once a day as part of rollover, so you can use that. This has the advantage it happens even if Cumulus has been stopped and restarted and rollover is happening during catch-up. | * Cumulus MX has option to list files to be transferred once a day as part of rollover, so you can use that to generate your extra copy. This has the advantage it happens even if Cumulus has been stopped and restarted and rollover is happening during catch-up. | ||
* A third party toll "Cumulus Toolbox" can also be used to transfer files at a particular time. Note this cannot tell whether Cumulus has done its rollover at the normal time, or during catch-up. | * A third party toll "Cumulus Toolbox" can also be used to copy/transfer files at a particular time. Note this cannot tell whether Cumulus has done its rollover at the normal time, or during catch-up. | ||
* There are other ways to specify that when a file changes it is copied somewhere. | * There are other ways to specify that when a file changes it is copied somewhere. | ||
*The system routines that Cumulus uses to access dayfile.txt require exclusive use of that file, so if you have any other process trying to access that file when Cumulus restarts, when Cumulus processes end of the (meteorological) day, or when a relevant option is selected from View or Edit menus, either your external process or the Cumulus process may fail. | *The system routines that Cumulus uses to access dayfile.txt require exclusive use of that file, so if you have any other process trying to access that file when Cumulus restarts, when Cumulus processes end of the (meteorological) day, or when a relevant option is selected from View or Edit menus, either your external process or the Cumulus process may fail. | ||
== Populating a database table == | == Populating a database table == | ||