Re: Interpreting Samba messages
On Thu, Aug 21, 2003 at 04:37:29PM +1200, Jonathan Chen wrote: > So what you're seeing is a conflict between the inetd.conf setup and > the persistent daemon setup. I'd recommend that you take out the > entries in /etc/inetd.conf. You're right. Thanks. Bob Hall ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Interpreting Samba messages
On Thu, Aug 21, 2003 at 12:26:27AM -0400, Bob Hall wrote: [...] > Samba works fine, so this doesn't seem to be a problem. But I'm > puzzled, probably because I don't know much about this. I'm guessing > that the error message occurs because inetd got to the port first. > But I thought that binding to a port was a prerequesite for listening > at the port. So if binding failed, why is nmbd listening at *:137? If you installed samba via the port, you *don't* need to make changes to /etc/inetd.conf. The port installs a startup script that invokes persistent smbd and nmbd deamons on startup. So what you're seeing is a conflict between the inetd.conf setup and the persistent daemon setup. I'd recommend that you take out the entries in /etc/inetd.conf. Cheers. -- Jonathan Chen <[EMAIL PROTECTED]> -- Computers are like air conditioners. They stop working when you open Windows. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Interpreting Samba messages
I get the following messages at startup; Aug 20 23:59:46 kongemord nmbd[284]: [2003/08/20 23:59:46, 0] nmbd/asyncdns.c:st art_async_dns(148) Aug 20 23:59:46 kongemord nmbd[284]: started asyncdns process 286 Aug 20 23:59:46 kongemord nmbd[284]: [2003/08/20 23:59:46, 0] lib/util_sock.c:op en_socket_in(804) Aug 20 23:59:46 kongemord nmbd[284]: bind failed on port 137 socket_addr = 0.0 .0.0. Aug 20 23:59:46 kongemord nmbd[284]: Error = Address already in use I would get similar messages for smbd, but I've configured it to bind only to the internal interface. sockstat shows root nmbd 3610 udp4 *:137 *:* ... root inetd 2035 udp4 *:137 *:* (My firewall blocks external CIFS connections, BTW.) Samba works fine, so this doesn't seem to be a problem. But I'm puzzled, probably because I don't know much about this. I'm guessing that the error message occurs because inetd got to the port first. But I thought that binding to a port was a prerequesite for listening at the port. So if binding failed, why is nmbd listening at *:137? And why are both nmdb and inetd listening at the same port? I thought you could have only one process listening at a port. Bob Hall ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
