WHATSNEW: Document that CTDB now follows Samba configure options

For locks, PID files and sockets.

Signed-off-by: Martin Schwenke <mschwenke@ddn.com>
Reviewed-by: Anoop C S <anoopcs@samba.org>
Autobuild-User(master): Martin Schwenke <martins@samba.org>
Autobuild-Date(master): Mon Jul 13 13:59:00 UTC 2026 on atb-devel-224

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 4e0ce68a5b69003296bcf9059c2add4eb1ee6b4e..f8b902efdc48418301c2a9386cb6b3167f626b58 100644 (file)
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -33,6 +33,19 @@ addresses CVE-2026-20833.
 CTDB changes
 ------------
 
+* CTDB's locations for locks, PID files and sockets now use ctdb/
+  subdirectories of the Samba locations configured at build time.
+  This means that the relevant top-level Samba configure options
+  (--with-lockdir, --with-piddir, --with-sockets-dir) are now also
+  used by CTDB.
+
+  The standalone CTDB build does not support these options.  However,
+  it is generally only used for developer/standalone testing.
+
+* The CTDB initscript (ctdb.init) has been moved to ctdb/doc/examples.
+  This recognises that it isn't installed by default so it is
+  basically unmaintained and untested.
+
 * Monitoring of (infrastructure) hosts is now supported.  A good use
   of this is to monitor DNS servers.  See the NETWORK MONITORING
   section in ctdb-script.options(5) for more details.