1 WHATS NEW IN Samba 2.2.0alpha2
2 ==============================
4 This is the third alpha release of the new 2.2.0 codebase
5 for Samba. This version must not be run in production.
7 This code will almost certainly have some bugs and is
8 intended to help the Samba Team prepare an official 2.2.0
11 The documentation in this alpha snapshot is not up to date,
12 there are many new parameters since 2.0.7 and some defaults
13 have changed. This will be corrected in a later alpha release.
15 A known problem is this version of Samba will not act as a PDC
16 for Win2k clients (although it works as a member server in a
17 Win2k hosted domain). This is being actively worked on and
18 it is intended this be fixed before 2.2.0 release.
20 Several significant bugs have been fixed between alpha2
21 and alpha2, these include :
23 Inclusion of mapping of NT ACLs to Linux ACLs, using the patch
24 found at http://acl.bestbits.at.
26 This is being done via an abstract interface that needs porting
27 to the following UNIXes - IRIX, Solaris, HPUX, AIX - as many
28 as can be done will be supported at 2.2.0 release. Please look
29 at the code in lib/sysacls.c for the needed work.
31 Addition of tdb spinlock code for tdb speed.
32 Addition of user list lookup from Win2k (thanks to the Samba TNG
33 branch code for this).
34 Addition of generic to specific mapping of security descriptors
36 Addition of code page 857 (Turkish).
37 Addition of "%D" substitution for incoming Domain of user.
38 getpwnam/getpwuid cache.
39 Many codepage fixes when dealing with printers with extended
40 characters (thanks to HP for this fix).
41 Inherited security descriptors for printing.
42 Creation of internal NT "token" for smbd access checks.
43 Addition of NT trans code for client.
44 Fix for inheritance of blocked signals (thanks to HP).
45 Addition of "total print jobs" parameter.
46 Fix for NT not being able to save properties changes on
48 Fixes to speed up enumeration of print jobs.
49 Cleanup printer spool files on client disconnect.
50 Byteswap fixes for printing code (thanks JF).
51 New parameter "dos filemode" to allow a user who can write to a
52 file to change permissions on it.
53 Subtle statcache bugfix.
54 Fix for Office2000 print to file bug.
55 Fix for MS Access multi-user open problem.
56 Valid users now in linked list rather than array.
57 SMB lookup now table driven rather than linear search (doh!).
58 TDB locking fixes for multiple openers.
60 Several significant bugs have been fixed between alpha0
61 and alpha1, these include :
63 Fix for level II oplock bug.
64 Support for detecting version 2/3 printer drivers (from HP).
65 Samba profiling support (from SGI).
66 Winbind integration fixes.
67 Preliminary Win2K PDC support in compatibility mode for Win2K
69 VFS interface updates.
70 Failover finding of BDC's now works again.
71 lpq race condition fixes.
73 SWAT username detection fix.
74 Bugfix for WinNT and Win2K point and print feature.
76 The upcoming 2.2.0 Samba release will include the following
79 Integration with the winbind daemon that provides a single
80 sign on facility for UNIX servers in Windows NT4/2000 networks
81 driven by a Windows NT4/2000 PDC.
83 Support for native Windows NT4/2000 printing RPCs.
84 This includes support for automatic printer driver
85 download. It is currently believed this functionality
88 Rewritten internal locking semantics for more robustness.
89 This alpha supports full 64 bit locking semantics on all
90 (even 32 bit) platforms. SMB locks are mapped onto POSIX
91 locks (32 bit or 64 bit) as the underlying system allows.
93 Conversion of various internal flat data structures to use
94 database records for increased performance and
97 Support for acting as a MS-DFS server
99 Compile time option for enabling a VFS layer
101 Support for server supported Access Control Lists (ACLs).
102 This support will require a specific pluggable backend to
103 be written for each filesystem ACL implementation to be
104 supported. The stable 2.2.0 release should contain
105 support for the following filesystems:
109 Linux Kernel 2.2 with German ACL patch
111 Currently in this alpha snapshot (alpha1) this feature
112 is not enabled - the VFS layer has been modified to allow
113 it, but the code is still under development and should
114 be in a later alpha snapshot.
116 Other platforms will be supported as resources are
117 available to test and implement the encessary modules. If
118 you are interested in writing the support for a particular
119 ACL filesystem, please join the samba-technical mailing
120 list and coordinate your efforts.
122 Support for collection of profile information. A shared
123 memory area has been created which contains counters for
124 the number of calls to and the amount of time spent in
125 various system calls and smb transactions. See the file
126 profile.h for a complete listing of the information
127 collected. Sample code for a samba pmda (collection agent
128 for Performance Co-Pilot) has been included in the pcp
131 To enable the profile data collection code in samba, you
132 must compile samba with profile support (run configure with
133 the --with-profile option). On startup, collection of data
134 is disabled. To begin collecting data use the smbcontrol
135 program to turn on profiling (see the smbcontrol man page).
136 Profile information collection can be enabled for all smbd
137 processes or one or more selected processes. The profiling
138 data collected is the aggragate for all processes that have
141 With samba compiled for profile data collection, you may see
142 a very slight degradation in performance even with profiling
143 collection turned off. On initial tests with NetBench on an
144 SGI Origin 200 server, this degradation was not measureable
145 with profile collection off compared to no profile collection
148 With count profile collection enabled on all clients, the
149 degradation was less than 2%. With full profile collection
150 enabled on all clients, the degradation was about 8.5%.
153 =====================================================================
155 If you think you have found a bug please email a report to :
159 As always, all bugs are our responsibility.