Date: Sat, 17 Feb 2018 08:52:24 +0000 From: bugzilla-noreply@freebsd.org To: apache@FreeBSD.org Subject: [Bug 225499] www/apache24: child pid exit signal Segmentation fault Message-ID: <bug-225499-16115-7VXMdZjUXU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225499-16115@https.bugs.freebsd.org/bugzilla/> References: <bug-225499-16115@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225499 --- Comment #11 from O. Hartmann <ohartmann@walstatt.org> --- (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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225499-16115-7VXMdZjUXU>