summaryrefslogtreecommitdiff
path: root/WHATSNEW.txt
diff options
context:
space:
mode:
authorKarolin Seeger <kseeger@samba.org>2017-06-26 13:18:50 +0200
committerJeremy Allison <jra@samba.org>2017-06-27 03:19:19 +0200
commit37db3d22e2cffae61398f5452fbe24b55a7da15b (patch)
tree98a85eb1efaa6e46fa173a565dc06066ef14c14b /WHATSNEW.txt
parent8ee4f8236830eb3fa1b273fa6927792a800f86bd (diff)
downloadsamba-37db3d22e2cffae61398f5452fbe24b55a7da15b.tar.gz
WHATSNEW: Fix typo...
and add some new/changed parameters. Signed-off-by: Karolin Seeger <kseeger@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org> Autobuild-User(master): Jeremy Allison <jra@samba.org> Autobuild-Date(master): Tue Jun 27 03:19:19 CEST 2017 on sn-devel-144
Diffstat (limited to 'WHATSNEW.txt')
-rw-r--r--WHATSNEW.txt52
1 files changed, 27 insertions, 25 deletions
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 8b646f92130..cca7e0bc7c9 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -51,7 +51,7 @@ value 1024-1300 to 49152-65535. This port range is not only used by a
Samba AD DC but also applies to all other server roles including NT4-style
domain controllers. The new value has been defined by Microsoft in Windows
Server 2008 and newer versions. To make it easier for Administrators to control
-those port ranges we use the same default and make it configureable with the
+those port ranges we use the same default and make it configurable with the
option: 'rpc server dynamic port range'.
The 'rpc server port' option sets the first available port from the new
@@ -76,7 +76,6 @@ authentication, SMB and RPC authorization is covered, however password
changes are not at this stage, and this support is not currently
backed by a testsuite.
-
Query record for open file or directory
---------------------------------------
@@ -85,29 +84,6 @@ queried through the 'net tdb locking' command. In clustered Samba this
can be useful to determine the file or directory triggering
corresponding "hot" record warnings in ctdb.
-
-Parameter changes
------------------
-
-The "strict sync" global parameter has been changed from
-a default of "no" to "yes". This means smbd will by default
-obey client requests to synchronize unwritten data in operating
-system buffers safely onto disk. This is a safer default setting
-for modern SMB1/2/3 clients.
-
-smb.conf changes
-================
-
- Parameter Name Description Default
- -------------- ----------- -------
- auth event notification New parameter no
- auth methods Deprecated
- map untrusted to domain New value/ auto
- Default changed/
- Deprecated
- profile acls Deprecated
- strict sync Default changed yes
-
Removal of lpcfg_register_defaults_hook()
-----------------------------------------
@@ -137,6 +113,32 @@ the talloc_autofree_context() (which is inherently thread-unsafe)
and still be valgrind-clean on exit. Modules that don't need to
free long-lived data on exist should use the NULL talloc context.
+Parameter changes
+-----------------
+
+The "strict sync" global parameter has been changed from
+a default of "no" to "yes". This means smbd will by default
+obey client requests to synchronize unwritten data in operating
+system buffers safely onto disk. This is a safer default setting
+for modern SMB1/2/3 clients.
+
+smb.conf changes
+================
+
+ Parameter Name Description Default
+ -------------- ----------- -------
+ allow unsafe cluster upgrade New parameter no
+ auth event notification New parameter no
+ auth methods Deprecated
+ map untrusted to domain New value/ auto
+ Default changed/
+ Deprecated
+ mit kdc command New parameter
+ profile acls Deprecated
+ rpc server dynamic port range New parameter 49152-65535
+ strict sync Default changed yes
+
+
KNOWN ISSUES
============