Re: cvs: php4 /ext/standard file.c
| From: | Sascha Schumann | Date: | Sat, 23 Dec 2000 15:06:27 +0000 |
| Subject: | Re: cvs: php4 /ext/standard file.c | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-3268@lists.php.net to get a copy of this message | ||
> So, how do we know it hadn't enough space in this case? Write can return
> partial write for any reason, theoretically, AFAIK.
That is the problem I outlined earlier. There is no way to
distinguish those two cases, AFAICT.
> 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?
Do you see any rationale behind terminating Apache when a
simple PHP script accesses a file which exceeds process
limits? I think it makes more sense to fail gracefully and
let operations continue.
- Sascha