From owner-freebsd-ports@FreeBSD.ORG Wed Jul 2 09:59:18 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6645CD72 for ; Wed, 2 Jul 2014 09:59:18 +0000 (UTC) Received: from mailhost.madaboutcable.com (mailhost.madaboutcable.com [88.96.254.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 226AF217F for ; Wed, 2 Jul 2014 09:59:17 +0000 (UTC) Received: from ws-w702-dr.ksm.pri ([192.168.5.50] helo=[127.0.0.1]) by mailhost.madaboutcable.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from ) id 1X2Gwf-0007Mh-5x for freebsd-ports@freebsd.org; Wed, 02 Jul 2014 10:35:21 +0100 Message-ID: <53B3D254.20901@ksm.co.uk> Date: Wed, 02 Jul 2014 10:35:16 +0100 From: Daren Organization: KSM Limited User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Hylafax on FreeBSD 10 and 100% CPU Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 140701-0, 01/07/2014), Outbound message X-Antivirus-Status: Clean X-Spam-Score: -1.0 (-) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 09:59:18 -0000 Hi I've tried installing Hylafax from ports on fresh FreeBSD 10. We previously had it running on an 8.2 system without issue. After starting faxgetty creeps up to and stays on 100% cpu. I did find a previous PR for this (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166071) which has the status of resolved fixed although people have requested it be re-opened as the problem is still occurring for them as well. I can add another comment to this if it helps get it noticed again, but my knowledge with C etc is non-existent to be able to help with it, although searching has come up with a similar/same issue on dragonflybsd (http://bugs.dragonflybsd.org/issues/2028) Does anyone know if this is being looked at? Thanks Daren