On 29 Feb 2012, at 01:13, Daevid Vincent wrote:
>> -Original Message-
>> From: Stuart Dallas [mailto:stu...@3ft9.com]
>>
>> Seriously? Errors like this should not be getting anywhere near your
>> production servers. This is especially true if you're really getting 30k
>> hits/s.
>
> Don'
Hi, Daevid
What you could do to have it quick is to install the plugin xdebug.
Here you can (as described in the documentation linked here) enable to get
some extra information for a E_* message from php.
http://xdebug.org/docs/stack_trace
I would not do that on a live-system where you have 30k
On Tue, Feb 28, 2012 at 3:14 PM, Daevid Vincent wrote:
> My question is, is there a way to enable some PHP configuration that would
> output more verbose information, such as a backtrace or the URL attempted?
>
Have you looked at log4php? [1] It's a log4j (Java based) logging
facility port to PHP
> -Original Message-
> From: Stuart Dallas [mailto:stu...@3ft9.com]
>
> Seriously? Errors like this should not be getting anywhere near your
> production servers. This is especially true if you're really getting 30k
> hits/s.
Don't get me started. I joined here almost a year ago. They did
On 28 Feb 2012, at 23:14, Daevid Vincent wrote:
> My question is, is there a way to enable some PHP configuration that would
> output more verbose information, such as a backtrace or the URL attempted?
>
> In our PHP error log, we have the usual semi-useful information. However
> this is only a p
On Tue, Feb 28, 2012 at 6:14 PM, Daevid Vincent wrote:
> My question is, is there a way to enable some PHP configuration that would
> output more verbose information, such as a backtrace or the URL attempted?
>
> In our PHP error log, we have the usual semi-useful information. However
> this is o
6 matches
Mail list logo
