Hi all,
I just released Samba 2.0.7pre2, available from :
ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gz
This is the second snapshot of the code that should become
the official Samba 2.0.7 and is feature complete (ie. I'm
only going to accept bug fixes, not more features).
This is *not* production code, but should work well as a
file and print server, and contains fixes for all known
Windows 2000 bugs.
Please download and test this code and report back any
problems to samba@samba.org. Your help in this will make
the official Samba 2.0.7 release better for everyone.
The RPM packaging for this release is not yet complete,
so only a source code tarball is being made available.
To everyone who contributed patches, many thinks, and
please download and test this code to ensure that the
functionality you wanted has been correctly implemented
in the code.
The updated part of the WHATSNEW.txt file follows.
Regards,
Jeremy Allison,
Samba Team.
--------------------------------------------------------
WHATS NEW IN Samba 2.0.7-pre2
============================
This is the latest stable release of Samba. This is the
version that all production Samba servers should be running
for all current bug-fixes.
TODO Before Official 2.0.7 release
----------------------------------
Update "Using Samba" html to match 2.0.7 code.
Update packaging code to include all new files.
New Documentation in 2.0.7
--------------------------
O'Reilly and Associates have donated their book "Using Samba"
to the Samba community to be updated in a collaberative way
along with the Samba software. Starting with this release the
html of "Using Samba" will be distributed with the Samba software
as the online documentation for Samba. Bug fixes for the book
are encouraged as is new material. Please help us make this
documentation the best it can be for Samba !
SWAT (Samba Web Administration Tool) has been updated to
add a link to the full text of "Using Samba" from the start
screen.
Note that this does not mean that the other documentation
(man pages especially) are being abandoned. The Samba Team
is still committed to updating and improving *all* the
documentation shipped with Samba.
Also, as the source code for the book is moved into a more
manageable format (not raw HTML) we are committed to making
it available for editing by all interested parties. The
current situation of only shipping HTML with the Samba software
is a first attempt at getting this documentation integrated
with the Samba software and should not be regarded as the only
way in which this material will be made available (it was just
the quickest way to get the book integrated into 2.0.7 :-).
Windows 2000 Issues
-------------------
This version of Samba has been tested with Windows 2000 and
the four known incompatibilities with Windows 2000 have been
fixed. See the "Changes in 2.0.7" list below for details.
New/Changed parameters in 2.0.7
-------------------------------
There is a new option to the autoconf "./configure" script.
This is the "--with-utmp" (and attendant "--without-utmp")
option. Running configure with this option will cause smbd
to attempt to use utmp accounting for users who log on and
log off to the Samba server.
There are 5 new parameters in the smb.conf file.
ump
utmp dir
These two parameters are only available if the "--with-utmp"
option was selected at configure time. The yes/no option "utmp"
specifies whether utmp records should be recorded on user
logon/logoff. It defaults to "no". The "utmp dir" (which
also has a synonym of "utmp directory") parameter is a
string parameter specifying a pathname to the directory containing
the utmp file databases. This defaults to "" (the empty string).
See the smb.conf man page for more details.
inherit permissions
This boolean parameter causes newly created files and directories
to inherit their initial permissions from their parent directory.
This can be very useful in propagating such things as the set-group
bit in directory heirarchies. See the smb.conf man page for more
details.
write cache size
This integer parameter specifies (in bytes) the size of a user level
per-file write cache that smbd will create for an oplocked file. This
can improve performance significantly for writing files by causing
writes to be done in large chunk sizes. If this parameter is set (it
defaults to zero which means no write cache) to the stripe size of
a raid volume then it will cause writes to be much more efficient.
Up to 10 write caches can be active simultaneously per smbd (allocated
for the first 10 oplocked file opens). All normal warnings about the
dangers of user level caching of data apply. See the smb.conf man page
for more details.
source environment
This pathname parameter causes Samba to read a list of environment
variables from a named file on startup. This can be useful in setting
up Samba in a clustered environment. See the smb.conf man page for more
details.
The default setting of the "level2 oplocks" parameter has changed from
False to True in this release.
Ability to delete users added
-----------------------------
SWAT and smbpasswd can now delete users from the Samba smbpasswd file.
See the man page for smbpasswd for details.
Roving profile behavior finalized
---------------------------------
The change in behavior with roving profiles (using the "logon home"
parameter instead of the "logon path" parameter) introduced in 2.0.6
has been discovered to be consistant with the way Windows NT behaves,
and has been left as the default action. Please see the additional
notes in the "logon home" parameter description in the smb.conf man
page for more details.
Changes in 2.0.7
-----------------
1). Fix for the semaphore promblems when compiling Samba with gcc on
SGI IRIX 6.5.x.
2). Quota support for Veritas filesystem added by David Lee.
3). Incoming RPC code re-written to support multiple PDU input from
the client. This should make the RPC subsystem more robust.
4). Fix from Ying Chen @ IBM to inline many frequently called functions. This
decreased CPU usage by 10%.
5). Fix from Ying Chen @ IBM to use a hash table to lookup entries in the file
cache. This is a significant improvement over the old linked-list
lookup code.
6). smbclient issues with native language support fixed. smbclient
now uses UNIX filename character sets exclusively when communicating
with libsmb library.
7). smbclient fix to not print error messages when "putting" an
empty file.
8). smbclient fix to cope with spaces in filenames when recursing.
9). Improved error reporting in smbclient when getting browse lists.
10). NetBIOS "scope" now supported in all Samba code/tools.
11). New mapping from code page 850 to UNIX "roman8" character set.
12). Fix for crash bug if debug file handle couldn't be opened.
13). Fix to allow mkdir to correctly set the high order permissions
bits for UNIX's that don't allow this by default.
14). Fix to dynamically allocate group array for setgroups. Don't
depend on NGROUPS_MAX being correctly defined in header files.
15). Fix for crash bug in floating point in snprintf.
16). "Safe" version of popen() included to allow use in code such
as "source environment" patch.
17). Fix for SWAT for trailing '\n' in asctime().
18). Wildcard match fix from weidel@multichart.de for NT wildcard
processing.
19). unix_mask_match fixes for "veto files" parameter.
20). Fix for system call bug when configuring on Linux kernel 2.0.x
with glibc2.1.x.
21). SO_REUSEPORT socket option added for HPUX.
22). All recv() calls changed back to read() to fix Solaris 2.5.x bug.
23). Some UNICODE conversion fixes. Not complete yet.
24). NetShareEnum fix for Windows 2000. Don't ask for 64K as Win2k
can't cope with this (returns "Out of memory" error).
25). Fixes for cli_error() crashes.
26). Fix for crash when connecting to password server by DNS name
not NetBIOS name.
27). Fix bug in demangling of compacted NetBIOS names.
28). Fixes for slow locking code for VMS.
29). Reply to short NetLogon packet in nmbd with short reply.
30). Correctly allign userdata to prevent crashes in nmbd.
31). Use talloc() in string buffer rotation code to prevent overwrites.
32). Added multi-byte awareness to parameter loading code.
33). Re-wrote password file modification code. We can now delete users
atomically. Original patch from Bruce Tenison.
34). Fixed bug in parsing smbpasswd type entries.
35). Fixes from HP to the windows registry RPC emulation.
36). Added ability to return RPC fault PDU to unknown calls. Needed to
allow Windows 2000 to return UNIX permissions as NT ACLs.
37). utmp code patch from T.D.Lee@durham.ac.uk. Not available on all
platforms - test with ./configure.
38). Inherit permissions fix from David Lee.
39). Added write caching code for oplocked files.
40). Workaround for new bug in Windows 2000 where NT file create using
NTtransact call sends UNICODE without bothering to set the UNICODE flag
bit.
41). Workaround for new bug in Windows 2000 where it attempts to re-write
existing ACLs to make them inherit only.
42). Removed unused mmap code.
43). Added correct implementation of share mode deny table. We now match
Windows NT.
44). Fix recursion bug with group enumeration.
45). Fix from Bjart Kvarme to take into account changed machine passwords
that haven't yet propagated from PDC to BDC.
46). Correctly skip two byte length field when accepting RPC "start of
message" packets in SMBwriteX on pipes.
47). Added auto-detection of Windows 2000 clients.
48). Fix bug with rollback of POSIX locks if a lock in a range fails to
apply.
49). Fix bug with registering startup smbd's in flat file.
50). Ensure usernames are converted correctly between DOS codepages
and UNIX character sets.
51). Fix for timestamps being set incorrectly on copied files from
Paul Eggert.
52). Fix for parsing HP specific printer definitions in make_printerdef.
--------------------------------------------------------
--
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------
Could you please modify source/config.sub, line 830 from:
| -eabi* | -ieee*)
to:
| -eabi* | -ieee* | -qnx*)
(Or add "-qnx*" to where you think is more appropriate...)
TIA,
Rick Lake
ANP, Dutch National Press Agency
Jeremy Allison wrote:>
> Hi all,
>
> I just released Samba 2.0.7pre2, available from :
>
> ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gz
>
> This is the second snapshot of the code that should become
> the official Samba 2.0.7 and is feature complete (ie. I'm
> only going to accept bug fixes, not more features).
>
> This is *not* production code, but should work well as a
> file and print server, and contains fixes for all known
> Windows 2000 bugs.
>
> Please download and test this code and report back any
> problems to samba@samba.org. Your help in this will make
> the official Samba 2.0.7 release better for everyone.
>
> The RPM packaging for this release is not yet complete,
> so only a source code tarball is being made available.
>
> To everyone who contributed patches, many thinks, and
> please download and test this code to ensure that the
> functionality you wanted has been correctly implemented
> in the code.
>
> The updated part of the WHATSNEW.txt file follows.
>
> Regards,
>
> Jeremy Allison,
> Samba Team.
>
Hello, I would like to add the following lines in source/include/includes.h for building on QNX: #include <sys/termio.h> #include <unix.h> Up to now, every new release I always manually add these to the already present ifdef QNX wrapper for DEFAULT_PRINTING (around line 39), resulting in: #ifdef QNX #define DEFAULT_PRINTING PRINT_QNX #include <sys/termio.h> #include <unix.h> #endif However, it has been suggested to use autoconf for this, instead of making this part of the code to QNX-ish. But I'm not familiar with autoconf. Can anyone show me a cleaner way of adding these lines somehow, somewhere? TIA, Rick Lake ANP Jeremy Allison wrote:> > Hi all, > > I just released Samba 2.0.7pre2, available from : > > ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gz > > This is the second snapshot of the code that should become > the official Samba 2.0.7 and is feature complete (ie. I'm > only going to accept bug fixes, not more features). > > This is *not* production code, but should work well as a > file and print server, and contains fixes for all known > Windows 2000 bugs. > > Please download and test this code and report back any > problems to samba@samba.org. Your help in this will make > the official Samba 2.0.7 release better for everyone. > > The RPM packaging for this release is not yet complete, > so only a source code tarball is being made available. > > To everyone who contributed patches, many thinks, and > please download and test this code to ensure that the > functionality you wanted has been correctly implemented > in the code. > > The updated part of the WHATSNEW.txt file follows. > > Regards, > > Jeremy Allison, > Samba Team. >
On Sat, 18 Mar 2000 15:00:20 +1100, hai scritto:>Hi all, > I just released Samba 2.0.7pre2, available from : >ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gzMy systems: rh61, 2.2.14 + smbfs-nls.patch. I refer to 2.0.7pre2 as 2.0.7 I know some of the following problems may be considered not worth the time needed to solve them, because they are not functional issues, however, here are my observations on 2.0.7 and 2.0.x in general. == 1) Samba seems to override unix permissions in a particular case. I get the very same behavior of: http://us1.samba.org/listproc/samba-technical/February2000/0476.html == 2) slow domain logon $ grep -v "^[#;]" /etc/samba/smb.conf|grep domain domain master = yes domain logons = yes $ no profiles, no login script. win98se is set NOT to use profiles, just a domain logon: [2000/03/19 12:19:58, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 0 [2000/03/19 12:19:58, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:03, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:03, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:03, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:03, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:08, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:08, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:08, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 [2000/03/19 12:20:08, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 10.0.0.172: code = 7 sometimes even more time == 3) smbclient: various weird things (at least for me) A) smbclient does not output anymore the line with "security=share" or "security=user" or "connected as guest security=user" after commands as "smbclient '\\srv\shr'" like 1.9.18 did. I think it was useful. B) "ls" of an empty dir B i) 1.9.18 doing "ls" to an empty samba dir: smb: \> ls 49550 blocks of size 16384. 33754 blocks available B ii) 2.0.7 doing "ls" to an empty samba dir: smb: \> ls ERRDOS - ERRbadfile (File not found.) listing \* 49550 blocks of size 16384. 33754 blocks available B iii) dir listing compatibility with win9x/nt When connecting with smbclient to a win share, the . and .. dir are showed in the top share too, even if .. obviously cannot be cd'ed into. I know . and .. in the topshare are useless, but if win does this way... If samba did like win9x/nt do, then the error at point ii) would go away automatically. C) putting just 1 of 2 dirs. I have a linux dir with dir1/file1 dir2/file2 I cannot find a way to connect to another smb server share and transferring just the dir1 with the file(s) within. smb: \> recurse directory recursion is now on smb: \> prompt prompting is now off smb: \> mask * smb: \> put dir1 dir1 does not exist smb: \> mput dir1 (dir1 is transferred without file1, no output) smb: \> mput dir* (dir1 and dir2 transferred without files, no output) smb: \> mput * (dir1 and dir2 transferred with files, output to screen) putting file dir1/file1 as \dir1\file1 (0.781235 kb/s) (average 0.78125 kb/s) putting file dir2/file2 as \dir2\file2 (1.46481 kb/s) (average 1.08507 kb/s) smb: \> I think "mput dir1" should do it, right? D) no output when transferring empty dirs "put" of empty dirs gives no output to the screen, even if the dirs are actually transferred, this causes confusion: smb: \> prompt prompting is now off smb: \> mput emptydir smb: \> recurse directory recursion is now on smb: \> mput emptydir smb: \> The 2nd mput really transfers the dir, the 1st does not, but the output is the same for both. == 4) browsing behavior: anonymous login There is a different behavior doing smbclient -L -U% if the server is samba or nt/w2k nt wants a correct user/pass pair if guest account is disabled, wants whatever user (even a wrong one, but it wants it) if guest account is enabled, example: smbclient -L nt -U% never shows the shares smbclient -L samba -U% shows the shares If nt has the guest account you need smbclient -L nt -Uany_wrong_user% to get the share Could -U% somehow trigger the use of the guest account on an nt machine with guest account enabled? == 5) docs - DOMAIN.txt is to be updated for logon_path/logon_home switch for win9x. - smbmount.txt: every occurrence of smb should be changed in smbfs - man smbmount: smb --> smbfs, mount.smb --> mount.smbfs - grepping the tarball for samba-bugs@samba.org give many matches. The last time I checked it, it told me it's now better to post to the samba@samba.org list. - A.Tridgell said that "writable" as no effect for a print share ---------- from an email on the list:> The setting of the writeable parameter doesn't seem to have any effect > on access to the printer so what does setting writeable = no actually > do?it doesn't do anything :) ---------- if this is true then the following example, and its comment, in man smb.conf [aprinter] path = /usr/spool/public writeable = false printable = true guest ok = true is misleading. The same is true for occurrences in PRINTER_DRIVER.txt and Faxing.txt. I think it's better to take out every writable/read only/write ok parameters from print shares examples if they don't do anything. == 6) sighup/log reopening logs. Even if the release notes of 2.0.6 say the issue is solved, this is not the case for my systems: connections that are already active keep logging to the old logs; logrotate rotates/zips the logs and samba stops logging completely till restart. However, Roger Hayter pointed me to the "copytruncate" option in logrotate: copytruncate Truncate the original log file in place after cre- ating a copy, instead of moving the old log file and optionally creating a new one, It can be used when some program can not be told to close its log- file and thus might continue writing (appending) to the previous log file forever. Note that there is a very small time slice between copying the file and truncating it, so some logging data might be lost. When this option is used, the create option will have no effect, as the old log file stays in place. I've been using this for sometime and this solves the samba logs rotating problem. I think you could put a note about "copytruncate" as a comment in the samba.log (logrotate config file) file, so that if someone has problems he can quickly see one possible solution. The "copytruncate" option didn't exist in old logrotate versions. == 7) wins-hook fires for group names <00> and <1E> (A.Tridgell said it should fire for unique names only) pre1 2000-02-17 10:23:12 add OEMWORKGROUP 00 518400 255.255.255.255 2000-02-27 11:00:49 add WORKGROUP 00 518400 255.255.255.255 2000-02-27 11:00:49 add WORKGROUP 1e 518400 255.255.255.255 2000-03-01 10:48:48 add WORKGROUP 00 518400 255.255.255.255 2000-03-01 10:48:48 add WORKGROUP 1e 518400 255.255.255.255 2000-03-01 18:44:21 add OEMWORKGROUP 00 518400 255.255.255.255 2000-03-06 21:27:45 add WORKGROUP 00 518400 255.255.255.255 2000-03-06 21:27:46 add WORKGROUP 1e 518400 255.255.255.255 2000-03-10 11:45:12 add OEMWORKGROUP 00 518400 255.255.255.255 2000-03-10 11:57:59 add OEMWORKGROUP 1e 518400 255.255.255.255 pre2 is the same 2000-03-18 15:10:23 add WORKGROUP 00 518400 255.255.255.255 2000-03-18 15:10:23 add WORKGROUP 1e 518400 255.255.255.255 == 8) smbmount: password length in "ps" output When a password protected win9x share is mounted, the username and the length of the password used to mount it are in the ps output. Could the length of the password be hidden? == 9) smbmount: weird problem with a weird setup If: - someone has and HD (Win9x) where the volume label of the HD is "Xyz" - there is a dir "c:\Xyz", - the c:\ rootdir is shared (say as "c") Then when the HD is smbmounted the c:\Xyz dir will appear as a file (really as a "VOLUME ARCHIVE") and not a dir, its content won't be available. To solve this either change the volume label or the dir name. Smbclient in not affected. This is real-time, if you change the volume label while the disk is smbmounted you see the dir re-becoming a dir and vice-versa. == 10) logging: connection attempts with wrong password samba doesn't log (at standard log level) the ip address of a machine from where a user tries to connect with a wrong password, or without being in "valid users". I'd like to know who is trying to access a non-public share using every possible password. Example: $ smbclient '\\myserver\myhome' -Ufffff%dddd produces on myserver [2000/03/18 13:52:32, 1] smbd/password.c:pass_check_smb(492) Couldn't find user 'fffff' in UNIX password database. [2000/03/18 13:52:32, 1] smbd/password.c:pass_check_smb(492) Couldn't find user 'fffff' in UNIX password database. No ip of client, double log (pre1 did just 1 line). == 11) logging: samba domain member There are two 2.0.7: the 1st is PDC, the other is domain member of the 1st PDC. Authentication works ok, the domain member has an empty smbpasswd file. When I connect to my homeshare on the domain member I get in the member logfile [2000/04/01 13:59:51, 1] smbd/password.c:pass_check_smb(500) Couldn't find user 'go' in smb_passwd file. [2000/04/01 13:59:52, 1] smbd/password.c:pass_check_smb(500) Couldn't find user 'go' in smb_passwd file. [2000/04/01 13:59:52, 1] smbd/service.c:make_connection(550) notebook (10.0.0.179) connect to service go as user go (uid=801, gid=801) (pid 969) (pre2 doubles the log, pre1 did not if I recall well) I don't understand why it logs that it can't find "go" in smbpasswd (twice) since the primary auth source is the pdc which gives ok to my userid/password pair. It shouldn't look at the smbpasswd file at all if the pdc is there online, should it? All works, but the log says something that could be interpreted as a problem. I routinely grep the logs for anomalies and these are false positives. Well, thanks for reading so far :-) Now about linux/samba: Could one of the SambaTeam members, you who have the "power", propose to A.Cox something along the lines of the smbfs-nls patch to definitely solve the problem with accented chars in smbmounted shares? Thanks. -- giulioo@pobox.com