From owner-freebsd-questions Fri Jan 19 9:12:29 2001 Delivered-To: freebsd-questions@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id C65A537B6A2 for ; Fri, 19 Jan 2001 09:12:10 -0800 (PST) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.11.1/8.9.3) with ESMTP id f0JHBrs09256; Fri, 19 Jan 2001 18:11:54 +0100 (CET) (envelope-from kheuer@gwdu60.gwdg.de) Date: Fri, 19 Jan 2001 18:11:53 +0100 (CET) From: Konrad Heuer To: Jeremiah Gowdy Cc: Subject: Re: Two Samba/FreeBSD questions In-Reply-To: <007601c08238$9bac1760$aa240018@cx443070b> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Jan 2001, Jeremiah Gowdy wrote: > > > Every time I start Samba, my log file shows this > > > > [2001/01/09 08:38:54, 0] lib/util_sock.c:set_socket_options(154) > > Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor) > > [2001/01/09 08:38:54, 0] lib/util_sock.c:set_socket_options(154) > > Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor) > > [2001/01/09 08:38:54, 0] lib/util_sock.c:set_socket_options(154) > > Failed to set socket option TCP_NODELAY (Error Bad file descriptor) > > [2001/01/09 08:38:54, 0] lib/util_sock.c:set_socket_options(154) > > Failed to set socket option IPTOS_LOWDELAY (Error Bad file descriptor= ) > > [2001/01/09 08:38:54, 0] lib/util_sock.c:set_socket_options(154) > > Failed to set socket option IPTOS_THROUGHPUT (Error Bad file descript= or) > > > > As though it's not using my socket options. It was working before, now > it's > > not. I tried searching for help on the subject, but all I got was a bu= nch > > of people asking and no one answering. > > >I think at least SO_KEEPALIVE should be a legal option. The error messag= e > >(Error Bad file descriptor) seems to indicate that samba tries > >setsockopt(2) on a non-socket file descriptor. > > That's how I understood it as well. However, I know TCP_NODELAY works. > It's not complaining about the option, it's complaining about the socket > itself. Is there a way to list the sockets in use and their socket optio= ns > ? What I'm wondering is if maybe this is just an obo error, or something > minor, but perhaps the real sockets are being properly set. I don't know how to listen socket *and* socket options; maybe it would help to start smbd with ktrace? You could study the ktrace log after that. Regards Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message