Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65725 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6144 invoked from network); 8 Feb 2013 06:57:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Feb 2013 06:57:02 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.213.173 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.213.173 mail-ye0-f173.google.com Received: from [209.85.213.173] ([209.85.213.173:47383] helo=mail-ye0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/70-32656-CB1A4115 for ; Fri, 08 Feb 2013 01:57:01 -0500 Received: by mail-ye0-f173.google.com with SMTP id l5so826714yen.18 for ; Thu, 07 Feb 2013 22:56:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=Qx5aWwRk8BqdpAPp81FgnG/eGQuPA3rS9Q/qSrU4lOc=; b=XdHjOVIoEK5ueks+aZsI15VbG7CkBiCWpztc/9o/1P7rgSTKY4PJE95CAwjnl69C9s B+TqYk9m8sH1PMu5ASXpfqYvcl+OBL5U0CEExtTx5h5fgZF+CltE0vVdBPixCFtYmB+C x3oWXqcEaMfyI7Rj1fHD9iopLHzr9dz97z6Vv/IyEOKBOhxkIzDCv3+WqPoS6v3YBma0 CG17VBSGVi0cRPLe44muEwLwpqlmpePdQKaQUbezY4o6l/NtmxbwYD2W9HayhPmx+Rqv AUQqGikO1ktGs1zO7gFnmVHid8u8enzjdPUJ0REIdllVSIOU+lvEsxoEq7gSW5ZwzzU0 E+CQ== X-Received: by 10.101.27.26 with SMTP id e26mr1416915anj.54.1360306618083; Thu, 07 Feb 2013 22:56:58 -0800 (PST) Received: from [172.16.8.146] (50-192-176-83-static.hfc.comcastbusiness.net. [50.192.176.83]) by mx.google.com with ESMTPS id h44sm51364531yhn.2.2013.02.07.22.56.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Feb 2013 22:56:57 -0800 (PST) Message-ID: <5114A1B8.3030305@lerdorf.com> Date: Thu, 07 Feb 2013 22:56:56 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Nikita Popov CC: Christoph Rosse , PHP internals References: <2B76A3EF-66AC-4E73-B186-236E9C2AE891@gmail.com> <5113AE8F.4060402@2bepublished.at> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlbeUgtzS1IQd2gqM7ZpV5r5HqjqUZGWj1HaAGaaEmtLphzv7abcBjBu4XxHv7JNtJOIRT2 Subject: Re: [PHP-DEV] [RFC] Improved Linux process title support in the CLI SAPI From: rasmus@lerdorf.com (Rasmus Lerdorf) On 02/07/2013 10:25 AM, Nikita Popov wrote: > On Thu, Feb 7, 2013 at 2:39 PM, Christoph Rosse wrote: > >> why wouldn't this go into core? setting the name of the current >> php-process is definitely something everyone that develops php-cli scripts >> could use. >> > I use a lot of php-cli scripts and I've never seen the need. Without having > hard data to back this up, I am pretty sure that this applies to nearly all > php-cli scripts. I think you may have glossed over the part where Keyur explained that when running tons of Gearman workers under GearmanManager it makes things a lot easier if we had a working way to set the proctitle. As he explained, the pecl/proctitle way of doing it isn't sufficient because it is likely to corrupt memory if you try to set the process title to anything longer than 3 characters. The only way to fix that memory corruption is to hook in earlier and that isn't something we can do from an extension. Note that other SAPIs have the same need. The FPM SAPI does something similar and for similar reasons. Whenever you are running any sort of process manager, it is super useful to be able to tell what each individual process is doing at a particular time. -Rasmus