5,838
edits
Debug.log: Difference between revisions
m
→File growth and deletion
| Line 31: | Line 31: | ||
== File growth and deletion == | == File growth and deletion == | ||
A new file is created each time Cumulus is restarted, after deleting the oldest and renaming the other old files to maintain the naming sequence. If debugging is switched off, periodically a message, confirming that, is added to the '''debug.log''' file, so it grows in size even when full diagnostics are not being stored. | A new file is created each time Cumulus is restarted, after deleting the oldest and renaming the other old files to maintain the naming sequence. If debugging is switched off, periodically a message, confirming that as shown earlier, is added to the '''debug.log''' file, so it grows in size even when full diagnostics are not being stored. | ||
Entries are added to the '''cumulus.~og''' file while Cumulus is left running, regardless of whether debugging is on or off. | Entries are added to the '''cumulus.~og''' file while Cumulus is left running, regardless of whether debugging is on or off (see example above). | ||
To avoid loss (or inaccuracy) of readings being processed from your weather station, it is best if Cumulus is left running, and not restarted except when unavoidable. Consequently, the current diagnostic files will grow in size. If the file is left to grow too large, Cumulus will crash. Therefore, you may want to delete these files. | To avoid loss (or inaccuracy) of readings being processed from your weather station, it is best if Cumulus is left running, and not restarted except when unavoidable. Consequently, the current diagnostic files will grow in size. If the file is left to grow too large, Cumulus will crash. Therefore, you may want to delete these files. | ||