I saw you are using:
Kernel: Linux 3.10.0-rc4+ (SMP w/2 CPU cores)
Could you try with prepackaged kernel (or even just some non-rc)?
O.
On Tue, Aug 20, 2013 at 12:41 PM, wrote:
> > "Peter" == Peter Chubb writes:
>
> > "Ondřej" == Ondřej Surý writes:
> Ondřej> could you try that wit
> "Peter" == Peter Chubb writes:
> "Ondřej" == Ondřej Surý writes:
Ondřej> could you try that with some simple script?
Actually here's an even simpler script:
I find this behaves correctly on some machines. but not the one
running my webserver :-(
--
To UNSUBSCRIBE, email to debi
> "Ondřej" == Ondřej Surý writes:
Ondřej> could you try that with some simple script?
Simple scripts don't seem to show the problem. I see it on Owncloud
and on Ampache.
My *guess* as to what's happening is that there's some other timeout
using SIGPROF, that triggers the Execution Time Ex
Hi Peter,
could you try that with some simple script?
O.
On Mon, Aug 19, 2013 at 2:04 AM, Peter Chubb wrote:
> Package: php5
> Version: 5.5.1+dfsg-2
> Severity: normal
>
> Dear Maintainer,
> php5 seems to throw a maximum execution time exceeded immediately.
> I see this on owncloud and ampache
Package: php5
Version: 5.5.1+dfsg-2
Severity: normal
Dear Maintainer,
php5 seems to throw a maximum execution time exceeded immediately.
I see this on owncloud and ampache.
I've set the default timeout to 3600 (1 hour), but the error that time
limit is exceeded comes almost immediately.
Here's a
5 matches
Mail list logo
