Documentation of log file redirection to <stdout> updated
Since multiple processes can write logs simultaneously, and there is no explicit synchronization between them, logs redirected to stdout may interleave. When logging to the disk file, synchronization is obtained by using a combination of O_APPEND and O_SYNC flags when log file is being opened, which is not possible when <stdout> redirection is in use. So documentation is updated to cleanly notify that this is debug-only feature, not for regular use
This commit is contained in:
parent
6c2bc83ec9
commit
5d6123a046
@ -98,7 +98,7 @@ sections.
|
||||
\fBLogFile\fR=\fIfilename\fR
|
||||
Log file path. It can be either absolute or relative. If not specified,
|
||||
defaults to \fI./sesman.log\fR. If set to \fB<stdout>\fR, log will go to
|
||||
stdout, which is useful for debugging\fR
|
||||
stdout. Use for debugging only\fR
|
||||
|
||||
It is ignored in the [ChansrvLogging] section
|
||||
since the channel server creates one log file per display and instead uses the
|
||||
|
@ -230,7 +230,7 @@ The following parameters can be used in the \fB[Logging]\fR section:
|
||||
|
||||
.TP
|
||||
\fBLogFile\fR=\fI@localstatedir@/log/xrdp.log\fR
|
||||
This options contains the path to logfile. It can be either absolute or relative. If set to \fB<stdout>\fR, log will go to stdout, which is useful for debugging\fR
|
||||
This options contains the path to logfile. It can be either absolute or relative. If set to \fB<stdout>\fR, log will go to stdout. Use for debugging only\fR
|
||||
|
||||
.TP
|
||||
\fBLogLevel\fR=\fIlevel\fR
|
||||
|
Loading…
Reference in New Issue
Block a user