Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123380
Precedence: bulk
MIME-Version: 1.0
References: <CAP1Jc10EHNhfCwz9p0tSyrSLiskCFnz7Ae0aTtYFJ8snYmVNOQ@mail.gmail.com>
 <D474A4F3-16A8-492A-B76C-E240A3712DC9@cmpct.info>
In-Reply-To: <D474A4F3-16A8-492A-B76C-E240A3712DC9@cmpct.info>
Date: Tue, 21 May 2024 14:48:52 +0200
Message-ID: <CAP1Jc101ZmO98GWsxi0PJd1kZ50vKAvL6oiDq8LxoSrhJCUX_w@mail.gmail.com>
Subject: Re: [PHP-DEV] Switching max_execution_time from CPU time to
 wall-clock time and from SIGPROF to SIGALRM
To: Calvin Buckley <calvin@cmpct.info>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: arnaud.lb@gmail.com (Arnaud Le Blanc)

Hi Calvin,

> FWIW, Cygwin and IBM i are also using wall time, because these platforms
> don't do execution time.

Thank you for the additional info.

> IIRC, the difference between platforms with how
> max_execution_time is counted doesn't seem to be documented last I checked.

Currently the max_execution_time documentation has a note about that,
but it only mentions Windows:

> https://www.php.net/manual/en/info.configuration.php#ini.max-execution-time
> On non Windows systems, the maximum execution time is not affected by system calls, stream operations etc. Please see the set_time_limit() function for more details.

Best Regards,
Arnaud