Re: cvs: php4 /ext/standard file.c
| From: | Sascha Schumann | Date: | Sat, 23 Dec 2000 15:08:50 +0000 |
| Subject: | Re: cvs: php4 /ext/standard file.c | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-3270@lists.php.net to get a copy of this message | ||
On Sat, 23 Dec 2000, Zeev Suraski wrote:
> At 16:56 23/12/2000, Stanislav Malyshev wrote:
> >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?
>
> I'd be in favour of catching it and displaying a PHP-level fatal
> error. There's nothing magical about catching signals...
And what happens, if the authors of mod_perl, mod_dtcl,
mod_snake have the same idea? How is a PHP-level handler
supposed to deal with SIGXFSZ generated by other modules?
- Sascha