Re: nmbd fails when run from xinetd
Remco Blaakmeer <email@example.com> wrote:
> This is a typical /var/log/nmb, left by such an nmbd:
> 01/27/1998 02:25:16 netbios nameserver version 1.9.18alpha14 started
> Copyright Andrew Tridgell 1994-1997
> bind failed on port 137 socket_addr=126.96.36.199 (Address already in use)
Er... why is nmbd trying to bind to port 137. xinetd has to have this
port bound in order to start nmbd.
Is nmbd being started without any options? (It should be, I think.)
Can you verify whether xinetd is properly passing off a valid
socket for udp?
[Not that I've done enough with udp to know exactly what proper means..
but an strace -f on xinetd while this is happening ought to be rather
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .