Error Messages after Committed Config Changes
Wei-Gung Sun
Wei-Gung.Sun at jpl.nasa.gov
Thu Jan 3 18:28:03 GMT 2002
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 at jpl.nasa.gov
(818) 354-2311
More information about the samba
mailing list