From owner-freebsd-questions@FreeBSD.ORG Wed Aug 20 21:37:33 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE6D216A4C0 for ; Wed, 20 Aug 2003 21:37:33 -0700 (PDT) Received: from chen.org.nz (chen.org.nz [210.54.19.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB07943FD7 for ; Wed, 20 Aug 2003 21:37:32 -0700 (PDT) (envelope-from jonc@chen.org.nz) Received: from grimoire.chen.org.nz (localhost [127.0.0.1]) by chen.org.nz (8.12.9/8.12.9) with ESMTP id h7L4bTOG002959; Thu, 21 Aug 2003 16:37:29 +1200 (NZST) (envelope-from jonc@grimoire.chen.org.nz) Received: (from jonc@localhost) by grimoire.chen.org.nz (8.12.9/8.12.9/Submit) id h7L4bTCn002958; Thu, 21 Aug 2003 16:37:29 +1200 (NZST) Date: Thu, 21 Aug 2003 16:37:29 +1200 From: Jonathan Chen To: Bob Hall Message-ID: <20030821043729.GB2854@grimoire.chen.org.nz> References: <20030821042626.GA433@kongemord.krig.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030821042626.GA433@kongemord.krig.net> User-Agent: Mutt/1.4.1i cc: freebsd-questions@freebsd.org Subject: Re: Interpreting Samba messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2003 04:37:34 -0000 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 ---------------------------------------------------------------------- Computers are like air conditioners. They stop working when you open Windows.