From owner-freebsd-ports Tue Jan 30 15:39:17 2001 Delivered-To: freebsd-ports@freebsd.org Received: from dannyboy.worksforfood.com (adsl-207-68-83-103.chlstn.adsl.bellatlantic.net [207.68.83.103]) by hub.freebsd.org (Postfix) with ESMTP id E3BCA37B67D for ; Tue, 30 Jan 2001 15:39:00 -0800 (PST) Received: by dannyboy.worksforfood.com (Postfix, from userid 1000) id 95D885A55F; Tue, 30 Jan 2001 18:38:59 -0500 (EST) Date: Tue, 30 Jan 2001 18:38:59 -0500 From: Daniel Harris To: Brandon Fosdick Cc: ports@freebsd.org Subject: Re: Everybuddy problem Message-ID: <20010130183859.A5770@dannyboy.worksforfood.com> References: <3A773CD4.3DF9AF6A@glue.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A773CD4.3DF9AF6A@glue.umd.edu>; from bfoz@glue.umd.edu on Tue, Jan 30, 2001 at 05:14:44PM -0500 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 30, 2001 at 05:14:44PM -0500, Brandon Fosdick wrote: > I just cvsupped and rebuilt/installed world this morning. Afterwards > running everybuddy produces "bind: Address already in use". So I -snip- That would be bind(2), not bind the nameserver gizmo. Everybuddy creates a socket name eb_socke in the .everybuddy directory... Removing this before starting everybuddy works around the problem. Looking at the code I find eb_socket and not eb_socke mentioned... that's probably the angle I'd look at if I knew anything about code. I mailed jim a few days ago about this, FWIW. Should probably take up with the people that actually put everybuddy out. -- Daniel Harris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message