SAMBA is slow.
Joel Hammer
Joel at HammersHome.com
Thu Jan 24 04:47:03 GMT 2002
To find where any binary program looks for a file, this sort of trick often
works:
strings `which smbclient` grep smb.conf
returns:
-s smb.conf pathname to smb.conf file
/usr/local/samba/lib/smb.conf
So, it looks like my smbclient looks at /usr/local/samba/lib/smb.conf
Another trick is to start smbclient with an obviously bad option, like so:
smbclient -XXXXX
returns:
snipped lines
Version 2.2.2
-s smb.conf pathname to smb.conf file
-O socket_options socket options to use
-R name resolve order use these name resolution services only
-M host send a winpopup message to the host
Numerous lines snipped here
-b xmit/send buffer changes the transmit/send buffer (default: 65520)
XXXX: Not enough '\' characters in service
It seesms that the -s option allows to to specify your smb.conf location.
And, you can change the buffer size from the comamnd line with smbclient
with -b.
Joel
> not have any impact on the SAMBA services (in fact, removing the smb.conf
> file did not cause as much as a warning message). So, how do I find out where
> SAMBA expects its configuration file to be? I checked the man pages, and the
> file is where it is supposed to be according to the manual... Alternatively,
> can I force SAMBA to look for the smb.conf file at a different location? I
> know the -l option for the SAMBA daemon, but my machine is supposed to be a
> client, not a server. How do I tell programs like smbclient where to look for
> the configuration file?
>
More information about the samba
mailing list