Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 2001 18:11:53 +0100 (CET)
From:      Konrad Heuer <kheuer@gwdu60.gwdg.de>
To:        Jeremiah Gowdy <jgowdy@home.com>
Cc:        <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Two Samba/FreeBSD questions
Message-ID:  <Pine.BSF.4.31.0101191809570.9112-100000@gwdu60.gwdg.de>
In-Reply-To: <007601c08238$9bac1760$aa240018@cx443070b>

next in thread | previous in thread | raw e-mail | index | archive | help

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.31.0101191809570.9112-100000>