On 24 March 2011 14:10, Ben Clayton b...@irax.com wrote:
[...]
I then found that I had in my smb.conf the line
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
which had come forward from the old server.
These socket options have been mentioned several times on the mailing
list as
Thanks Ben for taking the time to share your experience.
I'm in the list for just a couple month and this is the first time I see
that using * socket options* is a bad policy.
---
*Santiago DIEZ
Directeur
**Portable: +33 6 37 90 81 98
Bureau: +33 9 70 44 77 87*
*32 boulevard de Strasbourg, 75010
On Fri, Mar 25, 2011 at 10:06:54AM +0100, Santiago DIEZ wrote:
Thanks Ben for taking the time to share your experience.
I'm in the list for just a couple month and this is the first time I see
that using * socket options* is a bad policy.
Question: Where did you read that it is good policy?
As I said, I'm in the list for just a few month so I never read anything
about *socket options*.
I think it's a good thing to know that in case I bump into this parameter on
one of my servers.
Thanks again Ben.
---
*Santiago DIEZ
Directeur
**Portable: +33 6 37 90 81 98
Bureau: +33 9 70 44 77 87*
I've been struggling for several days with an issue to which I found a
number of references, but few solutions, so wanted to put my experience
out there, in the hope that others may find it useful at some time.
A client company network of 10 WinXP Pro PCs and CentOS 4 server (a
Fujitsu
