Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13452
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 22 Oct 2004 12:33:51 +0100
To: internals@lists.php.net
Message-ID: <20041022113351.GC9117@redhat.com>
Mail-Followup-To: internals@lists.php.net
References: <20041022062249.GA8983@redhat.com> <4e89b42604102202533086a25d@mail.gmail.com> <20041022100842.GB9395@redhat.com> <200410221259.04475.edink@emini.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <200410221259.04475.edink@emini.dk>
User-Agent: Mutt/1.4.1i
Subject: Re: [PHP-DEV] _FILE_OFFSET_BITS=64 considered harmful
From: jorton@redhat.com (Joe Orton)

On Fri, Oct 22, 2004 at 12:59:04PM +0200, Edin Kadribasic wrote:
> However I consider crashing apache children with signal 25 when doing simple 
> is_file() or fopen() on large files really harmful. Apache flat out refuses 
> to start if you have enabled php error log and that file happen to be 2GB or 
> bigger.

For Linux at least that was fixed since 2.0.50, or are you using 1.3
still?

w.r.t is_file() or open(), can you give more details? open() on a >2Gb
file will give EFBIG not die with SIGXFSZ.  *writing* beyond 2Gb will
die with SIGXFSZ, yes, is that what you mean?  I had a patch to make
sure SIGXFSZ was ignored but didn't bother with it since the large
logfile stuff went in which solves the common problem.

Regards,

joe