From owner-freebsd-apache@freebsd.org Sat Feb 17 08:52:27 2018 Return-Path: Delivered-To: freebsd-apache@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BED0F1C5E2 for ; Sat, 17 Feb 2018 08:52:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 273866F1D9 for ; Sat, 17 Feb 2018 08:52:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DB1ADF1C5DC; Sat, 17 Feb 2018 08:52:26 +0000 (UTC) Delivered-To: apache@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B405BF1C5D8 for ; Sat, 17 Feb 2018 08:52:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4954D6F1D0 for ; Sat, 17 Feb 2018 08:52:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8B77517660 for ; Sat, 17 Feb 2018 08:52:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1H8qPjX055244 for ; Sat, 17 Feb 2018 08:52:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1H8qP8U055243 for apache@FreeBSD.org; Sat, 17 Feb 2018 08:52:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: apache@FreeBSD.org Subject: [Bug 225499] www/apache24: child pid exit signal Segmentation fault Date: Sat, 17 Feb 2018 08:52:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ohartmann@walstatt.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: apache@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 08:52:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225499 --- Comment #11 from O. Hartmann --- (In reply to Torsten Zuehlsdorff from comment #10) Checking /usr/ports/Mk/bsd.default-versions.mk reports: [...] # Possible values: 5.6, 7.0, 7.1, 7.2 PHP_DEFAULT?=3D 5.6 [...] So I guess there is a reason, why php=3D5.6 is still the default? If 5.6 is= still the default, we can consider this problem with opcache a serious issue that needs to be solved in 5.6! Most modules I watched being present on the systems in question are reeled = in by some ports's default settings. I do not care much about this issue, but = now, it became a serious problem because its paralysing our Apache sites, which = we use for SVN, RefDB, Nextcloud, bareos and other maintenance stuff. I'd rath= er like to isolate the opcache module from being build than starting rebuilding all PHP dependend ports according to switching towards php=3D7.1. Since I have no idea which ports relying on php 5.6 are reluctant to play w= ith 7.1, I do not want to figure that out by myself, since the boxes in question performing the build do not have lots of performance. Well, it would be ano= ther story if php 7.1 is becoming the new standard soon and there are few, clear= ly identifyable ports not playing well we do not use. I checked which ports are relying on www/php56-opcache: # pkg info -r www/php56-opcache php56-opcache-5.6.33: ZendFramework-2.3.3_2 php56-extensions-1.0 So I consider this issue a serious one and it could not be ignored in favou= r of 7.1. We do not use "special cases" so I fear other will suffer from the same issue sooner or later when this crap gets common in the package tree. --=20 You are receiving this mail because: You are the assignee for the bug.=