Samba 2.0.7pre2 snapshot released.
Giulio Orsero
giulioo at pobox.com
Sun Mar 19 11:37:04 GMT 2000
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.gz
My 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 at samba.org give many matches. The
last time I checked it, it told me it's now better to post to the
samba at 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 at pobox.com
More information about the samba
mailing list