Re: cvs: php4 /ext/standard file.c
| From: | Zeev Suraski | Date: | Sat, 23 Dec 2000 15:09:36 +0000 |
| Subject: | Re: cvs: php4 /ext/standard file.c | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-3269@lists.php.net to get a copy of this message | ||
At 16:56 23/12/2000, Stanislav Malyshev wrote:
I'd be in favour of catching it and displaying a PHP-level fatal error. There's nothing magical about catching signals... Zeev -- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/SS>> The rationale behind SIGXFSZ seems to be that a process SS>> should be terminated, if it exceeds process limits.If so, shouldn't we comply with that thought and let the process die? Like, if Unix standards guys think that's right for a process to die in this case, they should know better?