Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66062 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44627 invoked from network); 20 Feb 2013 17:42:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Feb 2013 17:42:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.171 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.210.171 mail-ia0-f171.google.com Received: from [209.85.210.171] ([209.85.210.171:63058] helo=mail-ia0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2C/96-19387-9FA05215 for ; Wed, 20 Feb 2013 12:42:17 -0500 Received: by mail-ia0-f171.google.com with SMTP id z13so7395669iaz.2 for ; Wed, 20 Feb 2013 09:42:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ByYSRiNT1U3tSA9ndaeuCv/vXHxZG3a6ky6d4P39w0I=; b=TGMYf7mDjOHso0ibVcCBxcF8li2gGEwOTSWjFDOmu904XlqqiZVJRX6SrXqMezhyff xwv89GrPkogQ00kdt4CzLfi2uZNtbtoTaJKYlTviK3dASN/CILxHeAd9IHLMvG9giJb6 jfpv8lAp0ER7xO2JlH9W4ynMbAEFUVo6RcxWQp+il7hM2uPizr0sq09InHF2VJaee2tb hrd+QpUoKkrRBD4jHkwyodFqq96/4hjIlstf4BWDJev+1Gzr+QW1wyCtG3t6yrldgYQB Ps26RyJTEmzJuhd8wNrAfwaF1oJs+grfpt80nZUim+AK40hInKBQg1D5WVZqBlBqCtgV BD5Q== MIME-Version: 1.0 X-Received: by 10.43.65.145 with SMTP id xm17mr9645296icb.35.1361382134723; Wed, 20 Feb 2013 09:42:14 -0800 (PST) Received: by 10.50.114.137 with HTTP; Wed, 20 Feb 2013 09:42:14 -0800 (PST) In-Reply-To: <8C.EB.22055.CC1B3805@pb1.pair.com> References: <8C.EB.22055.CC1B3805@pb1.pair.com> Date: Wed, 20 Feb 2013 18:42:14 +0100 Message-ID: To: Jason Gu Cc: PHP Internals Content-Type: multipart/alternative; boundary=bcaec51d29988b342d04d62b7a89 Subject: Re: [PHP-DEV] Should "apc.slam_defence" and "apc.write_lock" be turned on at the same time? From: tyra3l@gmail.com (Ferenc Kovacs) --bcaec51d29988b342d04d62b7a89 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, Oct 21, 2012 at 10:26 AM, Jason Gu wrote: > Hi Internals > > I wondering if "apc.slam_defence" and "apc.write_lock" should be turned o= n > at the same time? > > The default for APC v3.1.13 have both settings turned on. > > But the documentation says "apc.slam_defence is Deprecated by > apc.write_lock." > > http://www.php.net/manual/en/**apc.configuration.php#ini.apc.** > slam-defense > > So I'd like to know how should the settings be configured? > > Thanks > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > from a quick look and based on the documentation I think that the default values should be changed as there is no reason to have the slam_defense enabled, and on a related note the docs refer to this section as slam_defense being an integer which controls a percentage (so valid values are between 0 and 100) while the code seems to parse and store this as a boolean value. could somebody look into this and clarify the docs maybe? --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --bcaec51d29988b342d04d62b7a89--