| Line 1,024: |
Line 1,024: |
| | <th>Value</th> | | <th>Value</th> |
| | <th>Description</th> | | <th>Description</th> |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enabled</td>
| |
| − | <td>yes | no; default: <b>no</b></td>
| |
| − | <td>Turns the Stunnel service on or off. If this is unchecked, Stunnel instances will not start (even if they are enabled individually); therefore, it is necessary to check this field in order to make Stunnel active on the router.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Debug Level</td>
| |
| − | <td>integer [0..7]; default: <b>5</b></td>
| |
| − | <td>Debugging to log output level.
| |
| − | <ul>
| |
| − | <li><b>0 (emergency)</b> - a panic condition, i.e., system is no longer usable.</li>
| |
| − | <li><b>1 (alert)</b> - a condition that must be corrected immediately.</li>
| |
| − | <li><b>2 (critical)</b> - critical conditions, device errors.</li>
| |
| − | <li><b>3 (error)</b> - errors that are fatal to the operation, but not the service or application (can't open a required file, missing data, etc.) Solving these types of errors will usually require user intervention.</li>
| |
| − | <li><b>4 (warning)</b> - anything that can potentially cause application oddities, but for which the system is automatically recovering from (e.g., retrying an operation, missing secondary data, etc.)</li>
| |
| − | <li><b>5 (notice)</b> - conditions that are not error conditions, but that may require special handling.</li>
| |
| − | <li><b>6 (info)</b> - general useful information (e.g., configuration changes, starts and stops of services, etc.)</li>
| |
| − | <li><b>7 (debug)</b> - contains basic information that is diagnostically helpful to most people (i.e., not just engineers).</li>
| |
| − | </ul>
| |
| | </tr> | | </tr> |
| | <tr> | | <tr> |
