From: Andrew Bartlett Date: Wed, 11 Jul 2018 23:56:40 +0000 (+1200) Subject: docs: Remove mention of --without-json-audit from the AD DC X-Git-Tag: tdb-1.3.16~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d55b1dc1be661a5e1d429f06b5e1557d6f106326;p=thirdparty%2Fsamba.git docs: Remove mention of --without-json-audit from the AD DC This is no longer optional for the AD DC. Signed-off-by: Andrew Bartlett Reviewed-by: Douglas Bagnall --- diff --git a/docs-xml/smbdotconf/logging/loglevel.xml b/docs-xml/smbdotconf/logging/loglevel.xml index ffd907508b6..9a029263070 100644 --- a/docs-xml/smbdotconf/logging/loglevel.xml +++ b/docs-xml/smbdotconf/logging/loglevel.xml @@ -74,18 +74,15 @@ Changes to the sam.ldb database are logged - under the dsdb_audit, and if Samba was not compiled with - --without-json-audit, a JSON representation is logged under + under the dsdb_audit and a JSON representation is logged under dsdb_json_audit. Password changes and Password resets are logged under - dsdb_password_audit, and if Samba was not compiled with - --without-json-audit, a JSON representation is logged under the + dsdb_password_audit and a JSON representation is logged under the dsdb_password_json_audit. Transaction rollbacks and prepare commit failures are logged under - the dsdb_transaction_audit, and if Samba was not compiled with - --without-json-audit, a JSON representation is logged under the + the dsdb_transaction_audit and a JSON representation is logged under the password_json_audit. Logging the transaction details allows the identification of password and sam.ldb operations that have been rolled back. diff --git a/docs-xml/smbdotconf/misc/dsdbeventnotification.xml b/docs-xml/smbdotconf/misc/dsdbeventnotification.xml index 6afc799e13d..7df46e1d68c 100644 --- a/docs-xml/smbdotconf/misc/dsdbeventnotification.xml +++ b/docs-xml/smbdotconf/misc/dsdbeventnotification.xml @@ -13,9 +13,7 @@ This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature - that the testsuite works around). Additionally Samba must be - not compiled with the --without-json-audit parameter for this - option to be effective. + that the testsuite works around). The Samba database events are also logged via the normal logging methods when the is diff --git a/docs-xml/smbdotconf/misc/dsdbgroupchangenotification.xml b/docs-xml/smbdotconf/misc/dsdbgroupchangenotification.xml index 2079f5145b2..6354979538b 100644 --- a/docs-xml/smbdotconf/misc/dsdbgroupchangenotification.xml +++ b/docs-xml/smbdotconf/misc/dsdbgroupchangenotification.xml @@ -13,9 +13,7 @@ This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature - that the testsuite works around). Additionally Samba must be - not compiled with the --without-json-audit parameter for this - option to be effective. + that the testsuite works around). The group events are also logged via the normal logging methods when the is diff --git a/docs-xml/smbdotconf/misc/dsdbpasswordeventnotification.xml b/docs-xml/smbdotconf/misc/dsdbpasswordeventnotification.xml index 62bf7ffc1fd..984321b98fc 100644 --- a/docs-xml/smbdotconf/misc/dsdbpasswordeventnotification.xml +++ b/docs-xml/smbdotconf/misc/dsdbpasswordeventnotification.xml @@ -13,9 +13,7 @@ This should be considered a developer option (it assists in the Samba testsuite) rather than a facility for external auditing, as message delivery is not guaranteed (a feature - that the testsuite works around). Additionally Samba must be - not compiled with the --without-json-audit parameter for this - option to be effective. + that the testsuite works around). The password events are also logged via the normal logging methods when the is