Dear List Members, Sorry to bother you with this, but I really do not know where else to get help. Searching the SAMBA and SuSE homepage did not shed any light on this problem, neither did mailings on two Linux User Groups, so this is sort of my last hope. I am trying to integrate my Linux PC into a mixed network of UNIX and Windows 2000 machines. Not quite a surprise, the integration with the UNIX part of the network was rather seamless, but I have big problems connecting to the Windows 2000 server. I got the connection sort of running, but only with a few B/s... Starting smbclient manually with the -b 1200 option (i.e. restricting buffersize to 1200 instead of 65500), sorted this problem; network speed went up to about 490 kB/s (it's a quite busy 10 MB/s Eithernet). However, as usual, sorting one problem creates two new ones: First, I do not always want to start any network service manually, mounting would be nice... Hence my wish to permanently reduce the buffersize to 1200. However, as far as I can tell, the configuratoin file for all SAMBA services seems to be smb.conf. I found this file, but according to the man entry, there is no such parameter as buffersize. My suspicion is that "max xmit" serves the same purpose, but setting that parameter did not bring any change. So question number one: which parameter do I set to what value to permanently force a reduction in buffersize from 65500 to 1200. Second, closely related to the first problem, I now have the suspicion that my SAMBA services do not find the smb.conf file, as doing changes did 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? I have reached the end of my knowledge here (in fact I reached it already quite a while ago, wild guessing is going on at the moment), so any tip would be greatly appreciated!!! Being a complete beginner on Linux, I would particularly appreciate any tips that do not involve any fancy maneuvers, like e.g. recompiling the kernel and stuff... Thank you in advance! Best wishes Thorsten -------------------------------------------------- Thorsten Brabetz Queen's University Belfast Electrical & Electronic Eng. Ashby Building, Stranmillis Road BELFAST, BT9 5AH UNITED KINGDOM Tel.: +44.(0)28.9027-4089 Fax: +44.(0)28.9066 7023 E-mail: T.Brabetz@ee.qub.ac.uk UIN: 5003405 --------------------------------------------------
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? >
Where Samba looks for the smb.conf depends on a) the version you use and b) if you installed the tar-Version or the rpm-Version shipped with SuSE. The Version shipped with SuSE normally looks for it in /etc/smb.conf. But when you install the tar-Version (thats what I did because I needed the new 2.2.2-Version) it will be looked for in /usr/local/samba/lib/smb.conf. My first mistake was to install first the rpm-Version and then over-installed the new one. SO I had two different smb.conf-files: On in /etc and one in /usr/local/samba/lib. UNfortunately I did every changes in /etc/smb.conf and was suprised that it had absolutely no effect on Samba, until I learned that there is another smb.conf:-) Maybe you did the same and therefore have the same "problem" as I had ? Stephan -----Urspr?ngliche Nachricht----- Von: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]Im Auftrag von Thorsten Brabetz Gesendet: Donnerstag, 24. Januar 2002 13:19 An: samba@lists.samba.org Betreff: SAMBA is slow. Dear List Members, Sorry to bother you with this, but I really do not know where else to get help. Searching the SAMBA and SuSE homepage did not shed any light on this problem, neither did mailings on two Linux User Groups, so this is sort of my last hope. I am trying to integrate my Linux PC into a mixed network of UNIX and Windows 2000 machines. Not quite a surprise, the integration with the UNIX part of the network was rather seamless, but I have big problems connecting to the Windows 2000 server. I got the connection sort of running, but only with a few B/s... Starting smbclient manually with the -b 1200 option (i.e. restricting buffersize to 1200 instead of 65500), sorted this problem; network speed went up to about 490 kB/s (it's a quite busy 10 MB/s Eithernet). However, as usual, sorting one problem creates two new ones: First, I do not always want to start any network service manually, mounting would be nice... Hence my wish to permanently reduce the buffersize to 1200. However, as far as I can tell, the configuratoin file for all SAMBA services seems to be smb.conf. I found this file, but according to the man entry, there is no such parameter as buffersize. My suspicion is that "max xmit" serves the same purpose, but setting that parameter did not bring any change. So question number one: which parameter do I set to what value to permanently force a reduction in buffersize from 65500 to 1200. Second, closely related to the first problem, I now have the suspicion that my SAMBA services do not find the smb.conf file, as doing changes did 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? I have reached the end of my knowledge here (in fact I reached it already quite a while ago, wild guessing is going on at the moment), so any tip would be greatly appreciated!!! Being a complete beginner on Linux, I would particularly appreciate any tips that do not involve any fancy maneuvers, like e.g. recompiling the kernel and stuff... Thank you in advance! Best wishes Thorsten -------------------------------------------------- Thorsten Brabetz Queen's University Belfast Electrical & Electronic Eng. Ashby Building, Stranmillis Road BELFAST, BT9 5AH UNITED KINGDOM Tel.: +44.(0)28.9027-4089 Fax: +44.(0)28.9066 7023 E-mail: T.Brabetz@ee.qub.ac.uk UIN: 5003405 -------------------------------------------------- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba