Re: [PHP] Outputting File To The Browser Failed And Kill Apache

2009-06-07 Thread Nitsan Bin-Nun
Whenever I will delete the symlink the file will be no more accessible? If so then what will happen if the user still downloading the file during the deletion of it? I'm pretty sure it will cause a stop of the downloading process at the client. I'm also not that much sure whether this is the right

Re: [PHP] Outputting File To The Browser Failed And Kill Apache

2009-06-05 Thread Tom Worster
if the problem is due to flow control issues between the script and the httpd server then perhaps changing the approach could help. i quit using this approach of writing files to the php output buffer a little while ago. it seemed that it was better to leave the flow control issues entirely to apa

Re: [PHP] Outputting File To The Browser Failed And Kill Apache

2009-06-05 Thread Nitsan Bin-Nun
My partner ran this command through SSH. This is the returned value: (as root) [r...@s1 ~]# ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > pending signals (-i) 397311 > max locke

[PHP] Outputting File To The Browser Failed And Kill Apache

2009-06-05 Thread Nitsan Bin-Nun
Hi List, I'm using the following code to output a file to the browser. Each file size is in the range of 5-10MB, all of them are MP3. header("Pragma: public"); > header("Expires: 0"); > header("Cache-Control: must-revalidate, post-check=0, pre-check=0"); > header("Cache-Control: public"); > heade