From owner-freebsd-stable Fri Feb 21 9: 6:35 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41A8237B401; Fri, 21 Feb 2003 09:06:34 -0800 (PST) Received: from mail.westbend.net (ns1.westbend.net [216.47.253.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09D3343FDD; Fri, 21 Feb 2003 09:06:33 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from ADMIN00 (WBIw005.westbend.net [216.47.253.25]) by mail.westbend.net (8.12.6/8.12.6) with SMTP id h1LH6VSG083643; Fri, 21 Feb 2003 11:06:31 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <000501c2d9cb$93a1fb10$19fd2fd8@westbend.net> From: "Scot Hetzel" To: Cc: Subject: d2cs fails to activate realm on 4.7 Date: Fri, 21 Feb 2003 11:06:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here's a head scratcher: I installed the games/bnetd port on FreeBSD 4.7, but when I tried to setup the d2cs server (which supports Diablo II games), the logs shows that the ream is created but never activated. Netstat does show the d2cs daemon connecting to the bnetd daemon. When I connect to the bnetd server with Diablo II, it gives an error that no realms are available. Now heres the scratcher: When I create a bnetd package of the 4.7 install, and then install it on FreeBSD 5.0-CURRENT, the bnetd.log file shows that the realm is created and active. I can connect to the bnetd server with Diablo II with no problems. Any ideals as to what could be causing this problem on 4.7? Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message