samba_2_0: some smbclient issues

[Giulio Orsero]

rh61, 2.2.14 + smbfs-nls.patch
SAMBA_2_0 as of 17 Jan 2000 19:43 GMT

=== 1)
smbclient 2_0 does not output anymore the line with
security=share
or
security=user
or
connected as guest security=user
or
...
after commands as "smbclient '\\srv\shr'".
It was useful.


=== 2) ls to an empty dirs
**** 2_0  or 1.9.18 doing "ls" to an empty win9x/winnt dir:

smb: \> ls
  .                               D        0  Wed Aug 11 07:05:12 1999
  ..                              D        0  Wed Aug 11 07:05:12 1999
 
                65248 blocks of size 16384. 4658 blocks available

**** 1.9.18 doing "ls" to an empty samba dir:
smb: \> ls
 
                49550 blocks of size 16384. 33754 blocks available

**** 2_0 doing "ls" to an empty samba dir:
smb: \> ls
ERRDOS - ERRbadfile (File not found.) listing \*
 
                49550 blocks of size 16384. 33754 blocks available

- Samba as a server never shows the 2 dirs  .  and  ..
- 2_0 gives an error.


=== 3) putting
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 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: \>


=== 4) winpopup charset problem
character set = iso8859-1
client code page = 850

samba -> win98 and win98 --> samba both give garbled chars in place of
accented chars in winpopup messages.


=== 5)
"put" of empty dirs give 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.


=== 6) weirdness
linux dirs:
dir1/file1  (size > 0)
dir2/file2  (size > 0)


smb: \> prompt
prompting is now off
(with or without smb: \> mask *)
smb: \> mput dir1
Error opening local file file1
smb: \>

an empty file1 is created on the target share.

if recurse is not set I think that smbclient should either transfer
nothing or just the top dir

-- 
giulioo at pobox.com