From 47f8af85f5ba97cd247b27dc8ee625ffbf1b93dd Mon Sep 17 00:00:00 2001 From: Zeev Suraski Date: Wed, 30 Aug 2000 18:06:17 +0000 Subject: [PATCH] This is no longer relevant... --- main/main.c | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/main/main.c b/main/main.c index 38f0d8c841..735d6c1b3c 100644 --- a/main/main.c +++ b/main/main.c @@ -473,16 +473,6 @@ PHP_FUNCTION(set_time_limit) } convert_to_long_ex(new_timeout); - /* FIXME ** This is BAD...in a threaded situation, any user - can set the timeout for php on a server wide basis. - INI variables should not be reset via a user script - - Fix what? At least on Unix, timers like these are - per-thread timers. Well, with a little work they will - be. If we use a bound thread and proper masking it - should work fine. Is this FIXME a WIN32 problem? Is - there no way to do per-thread timers on WIN32? - */ zend_unset_timeout(); zend_set_timeout(Z_LVAL_PP(new_timeout)); } -- 2.50.1