From owner-freebsd-questions Sat Dec 18 1:39:22 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 928CE14EAD for ; Sat, 18 Dec 1999 01:39:20 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id CAA24241; Sat, 18 Dec 1999 02:10:30 -0800 (PST) Date: Sat, 18 Dec 1999 02:10:30 -0800 (PST) From: Alfred Perlstein To: Martin Welk Cc: death , freebsd-questions@FreeBSD.ORG Subject: Re: Samba 2.0.6 & broken TCP_NODELAY option In-Reply-To: <19991217222754.E46333@theatre.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Dec 1999, Martin Welk wrote: > On Sat, Dec 18, 1999 at 05:37:49AM +1100, death wrote: > > > The smb.conf entry: > > > > socket options = TCP_NODELAY > > > > Doesn't work. Transfers to the samba server are dog slow at 200KB/s with or > > without the option. Transfers from the server are fine either way. > > A FAQ, a FAQ :-) Try > > socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=262144 \ > SO_RCVBUF=262144 > > and see my other mails in this list that deal with this problem :-) It's upsetting that even though we had people from the Samba team speaking at FreeBSD'con, they aren't making samba run as best it can under FreeBSD without obtuse hacks or socket options. Perhaps if anyone on the Samba team is listening you, can fix Samba's configure scripts to add these tweaks to the default install configuration? After all, isn't that what 'configure' is supposed to do? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message