samba-2.0.6pre2

[Giulio Orsero]

On Tue, 19 Oct 1999 19:55:27 +1000, hai scritto:

rh6/2.2.12/win9x (no nt)

In order of importance (for me):

1)
>- fixed SIGHUP log handling
This is not completely fixed: now new connections go to the new logs,
but connections that were active when the SIGHUP occurred keep logging
to the old logs (and it seems sometimes even new connections go to the
old log).


2)
I have problem with passwd sync: can change password 1 out of 5 times on
average, because of this error:
[1999/10/19 20:23:34, 3] smbd/chgpasswd.c:chat_with_program(365)
  Dochild for user go (uid=0,gid=0)
[1999/10/19 20:23:39, 3] smbd/chgpasswd.c:talktochild(262)
  response 3 incorrect
[1999/10/19 20:23:39, 3] smbd/chgpasswd.c:chat_with_program(312)
  Child failed to change password: go
[1999/10/19 20:23:39, 3] smbd/chgpasswd.c:chat_with_program(343)
  The process exited while we were waiting

I'm using:
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *Retype*new*UNIX*password* %n\n
*successfully*

Moreover, I have "passwd chat debug = Yes" but I don't get the chat
debug, it seems this param has no effect for me.


3)
I use:
logon path = \\%L\Profiles\%U
logon home = \\%L\%U
The command
net use h: /home 
maps h: to \\%L\Profiles instead of \\%L\%U


4)
oplock_break (and sighup)
[1999/10/20 13:44:17, 0] smbd/server.c:sig_hup(342)
  Got SIGHUP
[1999/10/20 13:44:17, 0] smbd/server.c:sig_hup(342)
  Got SIGHUP
[1999/10/20 13:44:17, 0] smbd/server.c:sig_hup(342)
  Got SIGHUP
[1999/10/20 13:44:17, 0] smbd/server.c:sig_hup(342)
  Got SIGHUP
[1999/10/20 13:53:02, 1] smbd/service.c:make_connection(534)
  notebook (10.0.0.179) connect to service share as user go (uid=500,
gid=500)(pid 9142)
[1999/10/20 13:53:43, 0] smbd/oplock.c:oplock_break(973)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file test/C.server Linux.awd (dev = 30a, inode
= 518156).
[1999/10/20 13:53:43, 0] smbd/oplock.c:oplock_break(1047)
  oplock_break: client failure in oplock break in file test/C.server
Linux.awd

Note that the log is from a file called log.smb.2, smbd received a
SIGHUP, and kept logging to the same file.

However, if I'm the only one to still get oplock_break after the recent
code changes, I can stop posting about this problem: setting "oplocks =
no" works for us, without a serious impact on performance as we have
just a 10Mbps network.


==the following are minor prolems

5)
This is common to previous versions:

when someone connects to a share, his ip is _always_ logged:
[1999/10/19 20:44:11, 1] smbd/service.c:make_connection(534)
  go (10.0.0.168) connect to service ...

when someone disconnects, _sometimes_ his ip is not logged:
[1999/10/19 20:59:11, 1] smbd/service.c:close_cnum(570)
  go (0.0.0.0) closed connection ....


6)
smbmount:
If:
- one 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.


7)
smbd -V
as non-root user doesn't say anything.
Wouldn't be possible to say "you need to run me as root to get my
version number"? It's just for simmetry with nmbd.


-- 
giulioo at tiscalinet.it