From owner-freebsd-questions@FreeBSD.ORG Thu Mar 4 06:48:35 2004 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 6401A16A4CE for ; Thu, 4 Mar 2004 06:48:35 -0800 (PST) Received: from bayok.msumain.edu.ph (unknown [203.177.105.166]) by mx1.FreeBSD.org (Postfix) with SMTP id 1970943D41 for ; Thu, 4 Mar 2004 06:48:32 -0800 (PST) (envelope-from rfa@msumain.edu.ph) Received: (qmail 4260 invoked from network); 4 Mar 2004 15:10:27 -0000 Received: from unknown (HELO bayok.msumain.edu.ph) (203.177.105.166) by bayok.msumain.edu.ph with SMTP; 4 Mar 2004 15:10:27 -0000 Received: from 203.177.105.170 (proxying for 192.168.16.12) (SquirrelMail authenticated user rfa) by bayok.msumain.edu.ph with HTTP; Thu, 4 Mar 2004 23:10:27 +0800 (PHT) Message-ID: <2443.203.177.105.170.1078413027.squirrel@bayok.msumain.edu.ph> Date: Thu, 4 Mar 2004 23:10:27 +0800 (PHT) From: rfa@msumain.edu.ph To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Subject: re: inetd[520] 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, 04 Mar 2004 14:48:35 -0000 followup on my question earlier about the warning inetd[520] ssh/tcp : bind; Address already in use I only got this message recently, and im sure i didnt do anything about inetd, also at the start of configuring freebsd, i confirmed sshd should run from inetd(i think).... anyway is there a way to confirm how sshd starts up? [the guy who respondd said sshd might be running out of sshd and consuming resources i think, i accidentally erased his email] i man'd inetd and saw that the configuration file was /etc/inetd.conf and i checked that out... i only uncommented sshd and ftpd so i don't think i am running sshd out of inetd.... can someone explain this baffling error? its coz of this i can't use web services from this box, although this box is still providing apache services.... yours, rommel