Release Announcements
=====================
-This is the first release candidate of Samba 4.1. This is *not*
+This is the first preview release of Samba 4.4. This is *not*
intended for production environments and is designed for testing
purposes only. Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
-Samba 4.1 will be the next version of the Samba suite and includes
-all the technology found in both the Samba4 series and the stable 3.x
-series. The primary additional features over Samba 3.6 are
-support for the Active Directory logon protocols used by Windows 2000
-and above.
-
-If you are upgrading, or looking to develop, test or deploy Samba 4.1
-releases candidates, you should backup all configuration and data.
+Samba 4.4 will be the next version of the Samba suite.
UPGRADING
=========
-
+Nothing special.
NEW FEATURES
============
-Directory database replication (AD DC mode)
-===========================================
-
-Directory replication has been reworked in order to improve the
-correctness and efficiency.
-As a net effect of it, replication with other domain controllers with
-a heavily modified schema is now possible (ie. Windows 2012 DCs or
-other Windows DC with exchange installed) and replication didn't fail
-anymore in such environments.
-
-
-Server-Side Copy Support
-========================
-
-Samba 4.1.0 adds support for server-side copy operations via the SMB2
-FSCTL_SRV_COPYCHUNK request. Clients making use of server-side copy
-support, such as Windows Server 2012, should experience considerable
-performance improvements for file copy operations, as file data need not
-traverse the network.
-This feature is enabled by default on the smbd file server.
-
-
-Btrfs Filesystem Integration
-============================
+Flush requests from SMB2/3 clients are handled asynchronously and do
+not block the processing of other requests. Note that 'strict sync'
+has to be set to 'yes' for Samba to honor flush requests from SMB
+clients.
-The Btrfs VFS module provided with Samba 4.1.0 further improves the
-performance of server-side copy operations on shares backed by a Btrfs
-filesystem. It does so by allowing multiple files to share the same
-on-disk extents, avoiding the unnecessary duplication of source and
-destination file data during a server-side copy operation.
-
-This feature can be explicitly enabled on smbd shares backed by a Btrfs
-filesystem with the smb.conf parameter:
-vfs objects = btrfs
-
-
-REMOVED COMPONENTS
-==================
-
-The Samba Web Administration Tool (SWAT) has been removed.
+WINS nsswitch module
+====================
+The WINS nsswitch module has been rewritten to address memory issues and to
+simplify the code. The module now uses libwbclient to do WINS queries. This
+means that winbind needs to be running in order to resolve WINS names using
+the nss_wins module. This does not affect smbd.
######################################################################
Changes
smb.conf changes
----------------
- Parameter Name Description Default
- -------------- ----------- -------
+ Parameter Name Description Default
+ -------------- ----------- -------
+ aio max threads New 100
- password level Removed
- set directory Removed
- use ntdb New No
+CTDB changes
+------------
+* The CTDB tunable parameter EventScriptTimeoutCount has been renamed
+ to MonitorTimeoutCount
-CHANGES SINCE 4.0.7
-===================
-
-o Michael Adam <obnox@samba.org>
+ It has only ever been used to limit timed-out monitor events.
+ Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will
+ cause CTDB to fail at startup. Useful messages will be logged.
KNOWN ISSUES
============
-
-RUNNING Samba 4.1 as an AD DC
-=============================
-
-A short guide to setting up Samba 4 as an AD DC can be found on the wiki:
-
- http://wiki.samba.org/index.php/Samba4/HOWTO
+Currently none.
#######################################
Reporting bugs & Development Discussion
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
-be filed under the Samba 4.1 product in the project's Bugzilla
+be filed under the Samba 4.3 product in the project's Bugzilla
database (https://bugzilla.samba.org/).
git.samba.org / obnox / samba / samba-obnox.git / blobdiff