From owner-freebsd-newbies@FreeBSD.ORG Mon Nov 15 20:59:55 2004 Return-Path: Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9115A16A4CE for ; Mon, 15 Nov 2004 20:59:55 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B5D643D41 for ; Mon, 15 Nov 2004 20:59:55 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 15 Nov 2004 14:56:21 -0600 Message-ID: <419918D2.7030503@daleco.biz> Date: Mon, 15 Nov 2004 15:00:02 -0600 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041023 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Trevor B. Sullivan" References: <8568FFD8B2D518499160B43B382844C938DD71@bwmail.corp.baxwood.com> In-Reply-To: <8568FFD8B2D518499160B43B382844C938DD71@bwmail.corp.baxwood.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Nov 2004 20:56:21.0843 (UTC) FILETIME=[8FCCAA30:01C4CB55] cc: "Charles.Tips.\[ceo\].SilentCircuit" cc: freebsd-newbies@freebsd.org Subject: Re: ssh/tcp: bind: Address already in use X-BeenThere: freebsd-newbies@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Gathering place for new users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 20:59:55 -0000 Charles.Tips wrote: >> var/log/messages has this every 10 minutes. Is it because sshd might be >> running out of inetd? If so what would be the solution to this? Thank >> you for any help. I am running freeBSD 5.2.1 p10 >> >> .Charlie > > { At this point I include the standard newbies@ disclaimer that the subject is better suited for the questions@ list .... } Trevor B. Sullivan wrote: > I'm having this same problem with the same version of FreeBSD(5.2.1). I > only noticed it after I enabled the sshd daemon. I haven't modified much > of anything, so I don't see how I could have caused this...would be > happy if someone had a solution. :-) > > Trevor Hmm, are you running sshd from inetd as well? sshd(8) is enabled by adding: sshd_enable="YES" to /etc/rc.conf. It is started at bootup and it seems likely that running it from inetd as well would cause an error message such as the one(s) you are describing. Kevin Kinsey