X-Git-Url: http://git.samba.org/?a=blobdiff_plain;f=WHATSNEW.txt;fp=WHATSNEW.txt;h=94ced206dbbf6e8d2fe12c289a0b00b532448be6;hb=063976fca375be367fa6b471389a3d7258b73460;hp=c9cd84faa2637069a9291a4e8e45166c67b24c3b;hpb=dad0c9a52eb142ea105231ab1e8df75ff00da210;p=samba.git

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index c9cd84faa26..94ced206dbb 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -16,6 +16,66 @@ UPGRADING
 NEW FEATURES/CHANGES
 ====================
 
+More succinct samba-tool error messages
+---------------------------------------
+
+Historically samba-tool has reported user error or misconfiguration by
+means of a Python traceback, showing you where in its code it noticed
+something was wrong, but not always exactly what is amiss. Now it
+tries harder to identify the true cause and restrict its output to
+describing that. Particular cases include:
+
+ * a username or password is incorrect
+ * an ldb database filename is wrong (including in smb.conf)
+ * samba-tool dns: various zones or records do not exist
+ * samba-tool ntacl: certain files are missing
+ * the network seems to be down
+ * bad --realm or --debug arguments
+
+Accessing the old samba-tool messages
+-------------------------------------
+
+This is not new, but users are reminded they can get the full Python
+stack trace, along with other noise, by using the argument '-d3'.
+This may be useful when searching the web.
+
+The intention is that when samba-tool encounters an unrecognised
+problem (especially a bug), it will still output a Python traceback.
+If you encounter a problem that has been incorrectly identified by
+samba-tool, please report it on https://bugzilla.samba.org.
+
+Colour output with samba-tool --color
+-------------------------------------
+
+For some time a few samba-tool commands have had a --color=yes|no|auto
+option, which determines whether the command outputs ANSI colour
+codes. Now all samba-tool commands support this option, which now also
+accepts 'always' and 'force' for 'yes', 'never' and 'none' for 'no',
+and 'tty' and 'if-tty' for 'auto' (this more closely matches
+convention). With --color=auto, or when --color is omitted, colour
+codes are only used when output is directed to a terminal.
+
+Most commands have very little colour in any case. For those that
+already used it, the defaults have changed slightly.
+
+ * samba-tool drs showrepl: default is now 'auto', not 'no'
+ 
+ * samba-tool visualize: the interactions between --color-scheme,
+   --color, and --output have changed slightly. When --color-scheme is
+   set it overrides --color for the purpose of the output diagram, but
+   not for other output like error messages.
+
+No colour with NO_COLOR environment variable
+--------------------------------------------
+
+With both samba-tool --color=auto (see above) and some other places
+where we use ANSI colour codes, the NO_COLOR environment variable will
+disable colour output. See https://no-color.org/ for a description of
+this variable. `samba-tool --color=always` will use colour regardless
+of NO_COLOR.
+
+
+
 
 REMOVED FEATURES
 ================