Home
last modified time | relevance | path

Searched refs:workers (Results 1 – 7 of 7) sorted by relevance

/PHP-8.1/
H A Drun-tests.php164 global $workers, $workerID;
363 $workers = null;
424 $workers = substr($argv[$i], 2);
425 if (!preg_match('/^\d+$/', $workers) || $workers == 0) {
426 … error("'$workers' is not a valid number of workers, try e.g. -j16 for 16 workers");
428 $workers = intval($workers, 10);
430 if ($workers === 1) {
431 $workers = null;
/PHP-8.1/ext/opcache/tests/
H A Dbug77434.phpt2 Bug #77434: php-fpm workers are segfaulting in zend_gc_addref
/PHP-8.1/sapi/fpm/
H A Dwww.conf.in420 ; Clear environment in FPM workers
422 ; by clearing the environment in workers before env vars specified in this
446 ; Additional php.ini defines, specific to this pool of workers. These settings
/PHP-8.1/sapi/cli/
H A Dphp_cli_server.c2393 char *workers = getenv("PHP_CLI_SERVER_WORKERS"); in php_cli_server_startup_workers() local
2394 if (!workers) { in php_cli_server_startup_workers()
2399 php_cli_server_workers_max = ZEND_ATOL(workers); in php_cli_server_startup_workers()
/PHP-8.1/sapi/fpm/tests/
H A Dlogtool.inc288 * Check workers output line.
/PHP-8.1/ext/opcache/jit/
H A Dzend_jit_x86.dasc9372 // TODO: ASLR may cause different addresses in different workers ???
10016 // TODO: ASLR may cause different addresses in different workers ???
H A Dzend_jit_arm64.dasc8753 // TODO: ASLR may cause different addresses in different workers ???
9300 // TODO: ASLR may cause different addresses in different workers ???

Completed in 75 milliseconds