canmove, Confirmed users
2,230
edits
MailNews:Logging: Difference between revisions
Jump to navigation
Jump to search
m
→Environment Variables to set: more workarounds for stomping on log file contents
m (correct Thunderbird_Logging lower case nit) |
m (→Environment Variables to set: more workarounds for stomping on log file contents) |
||
| Line 114: | Line 114: | ||
==== MOZ_LOG_FILE ==== | ==== MOZ_LOG_FILE ==== | ||
'''MOZ_LOG_FILE''' is the path and file name to the log file. An extension of '''.moz_log''' will be added to the file name (since Thunderbird 70). If MOZ_LOG_FILE is not set, then the output will be logged to the console where the application was launched. | '''MOZ_LOG_FILE''' is the path and file name to the log file. An extension of '''.moz_log''' will be added to the file name (since Thunderbird 70). If MOZ_LOG_FILE is not set, then the output will be logged to the console/terminal (stdout) where the application was launched. | ||
Example: | |||
<code>set MOZ_LOG_FILE=thunderbird-log-file</code> | |||
Note: | Note: | ||
* The log file is written over every time you re-launch the application. | * The log file is written over every time you re-launch the application. | ||
* If you | * You must have write access to the directory of the log file. The user's desktop directory or system temp directory are often a good choices. | ||
* | * If you run multiple applications at the same time, such as Firefox and Thunderbird, then might both write to the log file and possibly wipe out the other's log entries. Workarounds: | ||
** Run only one application at a time | |||
** Use the <code>append</code> option | |||
** Force logging to the console by setting MOZ_LOG_FILE to null, <code>MOZ_LOG_FILE=''</code>. | |||
==== MOZ_LOG ==== | ==== MOZ_LOG ==== | ||