|
4 | 4 | Workflow Logs
|
5 | 5 | =============
|
6 | 6 |
|
7 |
| -Cylc produces a number of log files which record information about the |
8 |
| -wortkflow, how it was installed, what tasks have run, their outcomes and more. |
| 7 | +Cylc produces log files which record information about how the workflow was |
| 8 | +installed, configured when started or changed, and about tasks that have run |
| 9 | +and their outcomes. |
9 | 10 |
|
10 | 11 |
|
11 | 12 | Log Files
|
@@ -36,7 +37,7 @@ Cylc log files are located in the workflow :term:`run directory`.
|
36 | 37 |
|
37 | 38 | .. describe:: log/config/flow-processed.cylc
|
38 | 39 |
|
39 |
| - The un-parsed contents of the ``flow.cylc`` (or ``suite.rc``) file that |
| 40 | + The unparsed contents of the ``flow.cylc`` (or ``suite.rc``) file that |
40 | 41 | the workflow was most recently started or restarted from. This file has
|
41 | 42 | not been parsed by Cylc so is still in the definition order, however,
|
42 | 43 | Jinja2 process has been performed making it useful for debugging Jinja2
|
@@ -92,7 +93,7 @@ Cylc log files are located in the workflow :term:`run directory`.
|
92 | 93 | ``type``
|
93 | 94 | Is either ``start``, ``restart`` or ``reload``.
|
94 | 95 | ``file_number``
|
95 |
| - Is initally ``1``, if the log file exceeds the `maximum size in bytes`, |
| 96 | + Is initially ``1``, if the log file exceeds the `maximum size in bytes`, |
96 | 97 | it will "roll over" into a new log file and this number will increment.
|
97 | 98 | If the number of "roll over" log files exceeds the
|
98 | 99 | `rolling archive length`, then Cylc will remove an old log file before
|
|
0 commit comments