From owner-freebsd-questions@FreeBSD.ORG Tue Jan 24 17:58:53 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 EFC3216A41F for ; Tue, 24 Jan 2006 17:58:53 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07A6743D48 for ; Tue, 24 Jan 2006 17:58:52 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: (qmail 23983 invoked by uid 1010); 24 Jan 2006 19:58:47 +0200 Received: from apircalabu.dsd.ro (10.10.15.22) by mail.bitdefender.com with AES256-SHA encrypted SMTP; 24 Jan 2006 19:58:47 +0200 Date: Tue, 24 Jan 2006 19:57:55 +0200 From: Adi Pircalabu To: Omer Faruk Sen Message-ID: <20060124195755.64892916@apircalabu.dsd.ro> In-Reply-To: <20060123113856.24662.qmail@istanbul.enderunix.org> References: <20060123113856.24662.qmail@istanbul.enderunix.org> Organization: BitDefender X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BitDefender-SpamStamp: 1.1.4 049000040111AAAAAAE X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.2 on mail.bitdefender.com X-BitDefender-Spam: No (0) Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.0-RELEASE apache13-modssl signal 11s X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 17:58:54 -0000 On Mon, 23 Jan 2006 13:38:56 +0200 Omer Faruk Sen wrote: > I have installed apache13-modssl 1.3.34+2.8.25_2 to my FreeBSD > 6.0-RELEASE. But when I try to start server using -DSSL I get signal > 11s. But when I disable mod_ssl httpd works fine. Does anybody lived > something like that with FreeBSD 6.0-RELEASE I've got something similar on 5.4, not tested on 6.0. The fix in my case was building the port against openssl-stable (i.e. 0.9.7i) Try building the port using WITH_OPENSSL_STABLE=YES Cheers -- Adi Pircalabu (PGP Key ID 0x04329F5E) -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/