From owner-freebsd-questions Fri Jan 19 8:53:15 2001 Delivered-To: freebsd-questions@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id 925DF37B69B for ; Fri, 19 Jan 2001 08:52:56 -0800 (PST) Received: from cx443070b ([24.0.36.170]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010119165051.VEED15630.femail4.sdc1.sfba.home.com@cx443070b>; Fri, 19 Jan 2001 08:50:51 -0800 Message-ID: <007601c08238$9bac1760$aa240018@cx443070b> From: "Jeremiah Gowdy" To: "Konrad Heuer" Cc: References: Subject: Re: Two Samba/FreeBSD questions Date: Fri, 19 Jan 2001 08:55:20 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 descriptor) > > 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 bunch > of people asking and no one answering. >I think at least SO_KEEPALIVE should be a legal option. The error message >(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 options ? 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. >/sbin/sysctl kern.maxfiles Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message