summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2011-09-13 12:05:00 +1000
committerAndrew Bartlett <abartlet@samba.org>2011-09-13 12:10:38 +1000
commit19d1c41fe5e88e5b186f7314df725e7ce3cb7646 (patch)
tree15d83ca8f7f3331ab80119794686f07eebcee478
parent0ee22a2dec1716e0d5c0a6aee612f635800af5ef (diff)
downloadsamba-19d1c41fe5e88e5b186f7314df725e7ce3cb7646.tar.gz
samba-19d1c41fe5e88e5b186f7314df725e7ce3cb7646.tar.bz2
samba-19d1c41fe5e88e5b186f7314df725e7ce3cb7646.zip
WHATSNEW: more information on running dbcheck
-rw-r--r--WHATSNEW.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 6b6e685d44..3fac3606a8 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -79,6 +79,21 @@ See also the -H option to point dbcheck at a different database to the
default, and the --fix and --yes options to make changes and to not
prompt about those changes.
+After upgrading Samba, it is suggested that you do the following:
+
+ - stop samba
+ - take a backup copy of your sam.ldb and sam.ldb.d/* database files
+ - run samba-tool dbcheck --cross-ncs --fix
+ - use 'all' to say yes to fixing each type of error found
+ - after it has finished, run dbcheck again to ensure it reports no
+ errors
+
+There will be a lot of errors fixed, particularly related to
+bad/missing GUID values. This is due to a bug in previous releases
+that left many objects with bad GUID values. These can all be fixed
+using dbcheck with steps above.
+
+
New default paths
-----------------