4 This is the first preview release of Samba 4.4. This is *not*
5 intended for production environments and is designed for testing
6 purposes only. Please report any defects via the Samba bug reporting
7 system at https://bugzilla.samba.org/.
9 Samba 4.4 will be the next version of the Samba suite.
20 Flush requests from SMB2/3 clients are handled asynchronously and do
21 not block the processing of other requests. Note that 'strict sync'
22 has to be set to 'yes' for Samba to honor flush requests from SMB
28 The WINS nsswitch module has been rewritten to address memory issues and to
29 simplify the code. The module now uses libwbclient to do WINS queries. This
30 means that winbind needs to be running in order to resolve WINS names using
31 the nss_wins module. This does not affect smbd.
33 ######################################################################
40 Parameter Name Description Default
41 -------------- ----------- -------
42 aio max threads New 100
47 * CTDB now uses a newly implemented parallel database recovery scheme
48 that avoids deadlocks with smbd.
50 In certain circumstances CTDB and smbd could deadlock. The new
51 recovery implementation avoid this. It also provides improved
54 * All files are now installed into and referred to by the paths
55 configured at build time. Therefore, CTDB will now work properly
56 when installed into the default location at /usr/local.
58 * Public CTDB header files are no longer installed, since Samba and
59 CTDB are built from within the same source tree.
61 * CTDB_DBDIR can now be set to tmpfs[:<tmpfs-options>]
63 This will cause volatile TDBs to be located in a tmpfs. This can
64 help to avoid performance problems associated with contention on the
65 disk where volatile TDBs are usually stored. See ctdbd.conf(5) for
68 * Configuration variable CTDB_NATGW_SLAVE_ONLY is no longer used.
69 Instead, nodes should be annotated with the "slave-only" option in
70 the CTDB NAT gateway nodes file. This file must be consistent
71 across nodes in a NAT gateway group. See ctdbd.conf(5) for more
74 * New event script 05.system allows various system resources to be
77 This can be helpful for explaining poor performance or unexpected
78 behaviour. New configuration variables are
79 CTDB_MONITOR_FILESYSTEM_USAGE, CTDB_MONITOR_MEMORY_USAGE and
80 CTDB_MONITOR_SWAP_USAGE. Default values cause warnings to be
81 logged. See the SYSTEM RESOURCE MONITORING CONFIGURATION in
82 ctdbd.conf(5) for more information.
84 The memory, swap and filesystem usage monitoring previously found in
85 00.ctdb and 40.fs_use is no longer available. Therefore,
86 configuration variables CTDB_CHECK_FS_USE, CTDB_MONITOR_FREE_MEMORY,
87 CTDB_MONITOR_FREE_MEMORY_WARN and CTDB_CHECK_SWAP_IS_NOT_USED are
90 * The 62.cnfs eventscript has been removed. To get a similar effect
91 just do something like this:
93 mmaddcallback ctdb-disable-on-quorumLoss \
94 --command /usr/bin/ctdb \
95 --event quorumLoss --parms "disable"
97 mmaddcallback ctdb-enable-on-quorumReached \
98 --command /usr/bin/ctdb \
99 --event quorumReached --parms "enable"
101 * The CTDB tunable parameter EventScriptTimeoutCount has been renamed
102 to MonitorTimeoutCount
104 It has only ever been used to limit timed-out monitor events.
106 Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will
107 cause CTDB to fail at startup. Useful messages will be logged.
109 * The commandline option "-n all" to CTDB tool has been removed.
111 The option was not uniformly implemented for all the commands.
112 Instead of command "ctdb ip -n all", use "ctdb ip all".
114 * All CTDB current manual pages are now correctly installed
121 #######################################
122 Reporting bugs & Development Discussion
123 #######################################
125 Please discuss this release on the samba-technical mailing list or by
126 joining the #samba-technical IRC channel on irc.freenode.net.
128 If you do report problems then please try to send high quality
129 feedback. If you don't provide vital information to help us track down
130 the problem then you will probably be ignored. All bug reports should
131 be filed under the Samba 4.3 product in the project's Bugzilla
132 database (https://bugzilla.samba.org/).
135 ======================================================================
136 == Our Code, Our Bugs, Our Responsibility.
138 ======================================================================