Parameter:
DEBUG_OUTFILE_UNIQUEShort description: Creates a separate, timestamped
Debug_Outfile on every server start instead of overwriting the existing one.Profile
Parameter | DEBUG_OUTFILE_UNIQUE |
Category | Logging / Debug |
Component | Server, Client |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = overwrite (default), 1 = unique file per start |
Description
The central log file addressed via
Debug_Outfile is normally overwritten on every server/client start. For longer error analyses (e.g. sporadic crashes or restart loops), this means previous logs are lost. With DEBUG_OUTFILE_UNIQUE=1, a timestamp/PID is automatically appended to the file name so that every session gets its own file.Example configuration
Debug_Outfile=C:\Domino\Debug\debug.txt DEBUG_OUTFILE_UNIQUE=1
Notes & pitfalls
- Don't forget to clean up – files accumulate.
- Pairs well with
DEBUG_CAPTURE_TIMEOUTand individualDEBUG_*flags.
- Indispensable for crash analyses, because otherwise the last run would be lost after the crash.
- A clear naming convention makes HCL Support uploads easier.
- Takes effect after a server/client restart.