samba - Jan 2002 - Error Messages after Committed Config Changes

Hi,

     My Samba server (Solaris 7, 64-bit mode) with AFS option has been 
running for a year.  I just changed the "Max Log Size" global
parameter few
times today.  Each time I committed the change, I got the following same 
set of error messages in my Samba log (the log.smb file):

[2002/01/03 17:40:56, 0] lib/util_sock.c:set_socket_options(151)
   Failed to set socket option SO_KEEPALIVE (Error Bad file number)
[2002/01/03 17:40:56, 0] lib/util_sock.c:set_socket_options(151)
   Failed to set socket option IPTOS_LOWDELAY (Error Bad file number)
[2002/01/03 17:40:56, 0] lib/util_sock.c:set_socket_options(151)
   Failed to set socket option TCP_NODELAY (Error Bad file number)
[2002/01/03 17:49:30, 0] lib/util_sock.c:set_socket_options(151)
   Failed to set socket option SO_KEEPALIVE (Error Bad file number)
[2002/01/03 17:49:30, 0] lib/util_sock.c:set_socket_options(151)
   Failed to set socket option IPTOS_LOWDELAY (Error Bad file number)
[2002/01/03 17:49:30, 0] lib/util_sock.c:set_socket_options(151)
   Failed to set socket option TCP_NODELAY (Error Bad file number)

The following is the global section of my smb.conf file:

# Global parameters
[global]
         netbios name = SAMBA01
         max log size = 500
         read size = 32768
         shared mem size = 5242880
         socket options = IPTOS_LOWDELAY TCP_NODELAY
         hide dot files = No

Anyone has same or similar problem?  I would appreciate any help.

Thanks.

Will Sun
wsun@jpl.nasa.gov
(818) 354-2311

Hi,

     I am trying to restrict or block SWAT's root access for dial-in from 
off-site except via VPN.  What config. or setup is needed on 
Samba/SWAT?  Anyone has same or similar development?  I would appreciate 
any help.

Thanks.

Will Sun
wsun@jpl.nasa.gov
(818) 354-2311

Hi,

The following message was repeated few times in the log.smb when user got 
access to a share (contained at least 10 files) on my Samba server, and 
couldn't see any files in that share (the share indicated 0 item at that
time).

[2002/09/12 09:38:36, 0] smbd/dir.c:dptr_close(280)
   Invalid key 0 given to dptr_close

After the user disconnected the access to the share, and then reconnected 
back to that share.  All files in that share appeared again, and no above 
message appeared in the log.smb.

Anything needs to be re-configured on my Samba server to prevent this from 
happening again?  Anyone has same or similar problem?  I would appreciate 
any help.

Thanks.


Will Sun
wsun@jpl.nasa.gov
(818) 354-2311