From owner-freebsd-ports@FreeBSD.ORG Tue Jul 14 08:00:55 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05ED4106564A for ; Tue, 14 Jul 2009 08:00:55 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from ibox.insign.ch (ibox.insign.ch [195.134.143.207]) by mx1.freebsd.org (Postfix) with SMTP id 532228FC13 for ; Tue, 14 Jul 2009 08:00:53 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 6912 invoked from network); 14 Jul 2009 07:34:11 -0000 Received: from [192.168.1.170] ([80.254.166.203]) by ibox.insign.ch ([195.134.143.207]) with ESMTP via TCP; 14 Jul 2009 07:34:10 -0000 From: Olivier Mueller To: ports@FreeBSD.org Content-Type: text/plain Date: Tue, 14 Jul 2009 09:34:10 +0200 Message-Id: <1247556850.20049.7.camel@ompc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit Cc: Subject: ejabberd 2.0.5 + erlang-r13b01_5 : failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2009 08:00:55 -0000 Hello, For the people around using ejabberd: erlang-r13b01_5,1 A functional programming language from Ericsson erlang-mysql-1.0_2 Native MySQL driver for Erlang ejabberd-2.0.5 Free and Open Source distributed fault-tolerant Jabber serv doesn't seem to work (epmd starts, but then nothings seems to happen and no log written), but after downgrading erlang, it's ok again: erlang-r12b5_2,1 A functional programming language from Ericsson erlang-mysql-1.0_2 Native MySQL driver for Erlang ejabberd-2.0.5 Free and Open Source distributed fault-tolerant Jabber serv I don't see the reason yet, I just get a bunch of erl_crash_20090714-nnnnn.dump files in /var/log/ejabberd with r13 and everything is fine with r12. But it is maybe related to a rather old freebsd version (7.0-RELEASE-p11). (no, it's not related to the uid/gid port change as specified in ports/UPDATING). regards, Olivier