SERVER-21677 Remove "diaglog" support from the server

1 files changed, 0 insertions, 86 deletions

diff --git a/debian/mongod.1 b/debian/mongod.1
index b775b7004d5..7982e554870 100644
--- a/debian/mongod.1
+++ b/debian/mongod.1
@@ -232,92 +232,6 @@ _
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-\-diaglog <value>
-\fIDefault\fP: 0
-.sp
-Deprecated since version 2.6.
-
-.sp
-\fI\%\-\-diaglog\fP is for internal use and not intended for most users.
-.sp
-Creates a very verbose \fIdiagnostic log\fP for troubleshooting and
-recording various errors. MongoDB writes these log files in the
-\fBdbPath\fP directory in a series of files that begin with the
-string \fBdiaglog\fP and end with the initiation time of the logging as a
-hex string.
-.sp
-The specified value configures the level of verbosity:
-.TS
-center;
-|l|l|.
-_
-T{
-Value
-T}	T{
-Setting
-T}
-_
-T{
-0
-T}	T{
-Off. No logging.
-T}
-_
-T{
-1
-T}	T{
-Log write operations.
-T}
-_
-T{
-2
-T}	T{
-Log read operations.
-T}
-_
-T{
-3
-T}	T{
-Log both read and write operations.
-T}
-_
-T{
-7
-T}	T{
-Log write and some read operations.
-T}
-_
-.TE
-.sp
-You can use the \fBmongosniff\fP tool to replay this output for
-investigation. Given a typical diaglog file located at
-\fB/data/db/diaglog.4f76a58c\fP, you might use a command in the following
-form to read these files:
-.INDENT 7.0
-.INDENT 3.5
-.sp
-.nf
-.ft C
-mongosniff \-\-source DIAGLOG /data/db/diaglog.4f76a58c
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
-.sp
-\fBWARNING:\fP
-.INDENT 7.0
-.INDENT 3.5
-Setting the diagnostic level to \fB0\fP will cause \fBmongod\fP
-to stop writing data to the \fIdiagnostic log\fP file. However,
-the \fBmongod\fP instance will continue to keep the file open,
-even if it is no longer writing data to the file. If you want to
-rename, move, or delete the diagnostic log you must cleanly shut
-down the \fBmongod\fP instance before doing so.
-.UNINDENT
-.UNINDENT
-.UNINDENT
-.INDENT 0.0
-.TP
 .B \-\-traceExceptions
 For internal diagnostic use only.
 .UNINDENT