search for: so_sndbuf

I've been in discussion with a colleague who had to reduce (!) SO_SNDBUF to get decent performance, and so wrote this little tool. It tells you the system default for most of the settable socket options. It can't do linger, as the value is a struct instead of an int, but that's probably uninteresting to Samba folks. Run this to see what you'd have if y...

...dev:295,0 ino:2692868 uid:65 gid:65 size:0 O_RDWR FD_CLOEXEC 6: S_IFIFO mode:0000 dev:295,0 ino:2692868 uid:65 gid:65 size:0 O_RDWR FD_CLOEXEC 7: S_IFSOCK mode:0666 dev:293,0 ino:33376 uid:0 gid:0 size:0 O_RDWR|O_NONBLOCK SOCK_STREAM SO_REUSEADDR,SO_KEEPALIVE,SO_SNDBUF(49152),SO_RCVBUF(49640),IP_NEXTHOP(0.0.193.232) sockname: AF_INET 134.84.119.102 port: 143 peername: AF_INET 160.94.23.17 port: 38847 8: S_IFSOCK mode:0666 dev:293,0 ino:63591 uid:0 gid:0 size:0 O_RDWR|O_NONBLOCK SOCK_STREAM SO_SNDBUF(16384),SO_RCVBUF(5120...

On Thu, Feb 04, 2016 at 09:03:21AM +0300, Владимир Терентьев wrote: > Hi. Try add this to your config in global section. > > socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_THROUGHPUT SO_RCVBUF=262140 > SO_SNDBUF=262140 Sorry to step in, but SO_SNDBUF and SO_RCVBUF are almost always bad for performance, unless you know *EXACTLY* what you're doing at a packet level. A general advice on a mailing list without VERY close analysis of the network infrastructure and operating system behaviour is very unlikel...

Dear friends, I receive the error "Error Bad file descriptor" when samba start, the socket option in smb.conf have the line: "socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=4096" My distribuition is Red Hat 6.2 and the Samba version is 2.0.69. This is the error log /var/log/samba.smb: [2000/08/31 14:07:06, 0] lib/util_sock.c:set_socket_options(148) Failed to set socket option SO_RCVBUF (Error Bad file descriptor) [2000/08/31 14:41:31, 0] lib/util_sock.c:set_so...

...en sending files to the server, the speed is OK. Since the databases used by that apllication have about 50Mb each, the problem must be caused by that slow speed on receiving files from the server. I've twiked the configuration a bit, and came to this results: socket options = SO_RCVBUF=65535 SO_SNDBUF=65535 TCP_NODELAY IPTOS_LOWDELAY - Very slow on reading, fast when writing socket options = TCP_NODELAY IPTOS_LOWDELAY - still slow on read, but a little better. Fast when writing socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=32768 - significant improvement when reading files, but the appli...

...and works quite well on everything but with Samba. I have played with the smb.conf to try to improve performance but to no avail. The setup is fairly simple. Here is my smb.conf [global] workgroup=HOME netbios aliases = MEDIALAB security = user socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 use sendfile = true local master = yes os level = 33 wins support = yes [homes] comment = Home Directories browseable = no writable = yes [musica] comment= Musica para alegrar la vida path = /media/external/Multimedia/Musica...

.... Apple's fault) ================================================== == Macbook to Ubuntu: 20 Mbps Macbook to Windows: 44 Mbps That's a significant change. So I changed the following line in Samba's smb.conf file: socket options = TCP_NODELAY SO_KEEPALIVE IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 to socket options = TCP_NODELAY SO_KEEPALIVE IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536 After this, I noticed the following: Wireless: ========= Macbook to Ubuntu: 44 Mbps, with peaks up to 48 Mbps. That's nearly double the performance!! Wireless is basically what I was unhappy a...

...lled by write_socket_data, then I read smb.conf, and I came across the following lines: # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details # Rather, the options do NOT work in some cases socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 After several trials, I modified the socket options to: socket options = TCP_NODELAY SO_RCVBUF=8192 ie, simply deleted the SO_SNDBUF=8192 Then, everything works perfectly now! I suggest that if anyone meets such 'write_sock_data', 'Broke pipe', etc errors, try something o...

...on of the client name or OS? Long version follows for the masochists! At home I run a mixed-client network, and I am having problems configuring my smb.conf to support them all equally well. I am able to create shares, and I can browse them, but file transfers can be very slow depending on my SO_SNDBUF and SO_RCVBUF settings. Unfortunately the magic numbers fall into 2 categories for different clients! My server is FreeBSD 4.9, with Samba 2.2.8 (compiled from the ports collection). I have fiddled with smb.conf and figured out this pattern: Client 1: WinXP. Best RCV/SNDBUF = 8192. Client 2: Po...

...db backend = smbpasswd         passdb backend = tdbsam #       server role = standalone server #       username map = /usr/local/etc/samba4/username.map         log level = 10         log file = /var/log/samba4/%m.log         max log size = 50 #       socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 #       socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072         socket options = TCP_NODELAY #       disable spoolss = Yes #       read raw = yes #       write raw = yes #       use sendfile = true #       strict locking = No         security = user         lo...

...size 65487 or less, then the writing speed is about 7-8 MB/s - a very nice value, my bow to the Samba team :) If I change the block size to 65488 or more, then the writing speed falls down to 3 MB/s, which is not what I expect from a 100Mbit network :\ Samba behaves this way even if SO_RCVBUF and SO_SNDBUF are set to 8192 and "read size" to 16384 and "max xmit" to 16384. The corresponding part of my smb.conf looks like this: client code page = 852 preserve case = yes socket options = TCP_NODELAY IPTOS_LOWDELAY IPTOS_THROUGHPUT SO_KEEPALIVE SO_RCVBUF=65535 SO_SNDBUF=6553...

Hello, Working a few servers that are transferring data across country with a 75ms delay on a GIGE connection. We can tune the tcp buffers on linux to improve the connections using iperf. Does rsync use the tcp buffers of the OS or does it override these settings? Thanks, Neal -------------- next part -------------- An HTML attachment was scrubbed... URL:

...est, winbind, sam map to guest = Bad User passdb backend = tdbsam:/opt/pware/samba/3.0.23d/private/passdb.tdb guest account = guest username map = /opt/pware/samba/3.0.23d/lib/smb_users.map log level = 0 name resolve order = wins lmhosts host bcast socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = No machine password timeout = 86400 preferred master = No local master = No dns proxy = No wins server = Myserver WINS ldap ssl = no winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes NOW, I need change NT for Active Directory WIN2...

...oxes on the lan with the following config file: [global] workgroup = PRINTSERVER netbios name = NEPTUN server string = neptun print server log file = /var/log/samba/log.%m max log size = 50 security = share encrypt passwords = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = lpstat printing = cups [printers] comment = All Printers printer = hp_670C path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes create mode = 0700 print command = lpr -P %p -o raw %s -r lpq command = lpstat...

...control, link ok Sound good, huh? Since people there are basic end user, I can't do any other test (FTP one, NFS one, and so on). But the funny thing is that a copy windows<->windows is far faster (more than 2 times faster). Same Switch. Well, STFW, see FAQ, got some infos about MTU and SO_SNDBUF stuff. I've change the SO_SNDBUF option, and use 16384 for value. A little better, but still slow. I haven't found a clear information about the MTU configuration and changes we must do for Samba. More, I read that changing MTU under Windows 98 is quite risky, and since they are basic end...

...smb.conf I am using currently ===SMB.CONF=== [global] workgroup = MYGROUP netbios name = {HOSTNAME} wins server = {WINSSERVER} server string = {HOSTNAME} security = SHARE encrypt passwords = Yes log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No oplocks = No level2 oplocks = No [homes] comment = Home Directories read only = No browseable = No [Data] comment = Data Backup Directory path = /home/gm/data guest account = valid users = spirian read only = No ====== I was wondering if there is any documentation...

...her (so I expect over 50MB/s when only reading this data). As you can see, the HDD subsystem is not the bottleneck for sure. Just for info, the XFS filesystem is used. In samba configuration, I was playing with socket options, (un)setting TCP_NODELAY, IPTOS_LOWDELAY and trying to set SO_RCVBUF and SO_SNDBUF parameters to different values starting from 8192 to 65535 in steps of 16k. These changes had almost no influence on the performance. As a last step I've also tried using the case sensitivity option for the concrete share (the 4 commented lines in the "mks" share in smb.conf file atta...

...ar/log/samba/smbd.log max log size = 10240 max xmit = 65535 dns proxy = No wins server = 192.168.10.10 ldap ssl = no create mask = 0775 hosts allow = 127., 192.168. cups options = raw socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 IPTOS_LOWDELAY -- Isaac Ojeda Llebry Servicio de Inform?tica y Comunicaciones de la ULPGC e-mail: iojeda en becarios.ulpgc.es Tel?fono: +34 928 459568

...server string = SoundServer %v realm = hunter.radiogong.intern admin users = root, administrator, sascha security = user dns proxy = yes wins proxy = Yes wins support = Yes ldap ssl = no socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 keepalive = 255 locking = 1 kernel oplocks = yes blocking locks = yes oplocks = yes level2 oplocks = yes large readwrite = yes map to guest = Bad User dos charset = ISO8859-15 unix charset = ISO8859...

...Samba Server Imbrium encrypt passwords = Yes smb passwd file = /etc/samba/smbpasswd unix password sync = Yes log level = 0 log file = /var/log/samba/log.%m max log size = 50 time server = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 logon script = netall.bat domain logons = Yes local master = Yes os level = 255 preferred master = Yes domain master = Yes wins support = Yes security = user This works fine. The problem is the Domain member server I am trying...