but using strace directly by attaching to processus can be risky in production (like gdb!)...
and with apache with 256 or 512 processuss all working can be hard to debug...
in some time have lost the processus...by attempting to attach to it...
and yes is very low level trace...
in first aproche debug log can usefull to see where the problem are and after can be useful to use strace/ltrace to deep into the problem...
debug trace can be usefull to encircle the problem...
and to have trace of internal information of apache is not very freindly in using strace/ltrace... than debug log that are trace important information...
i think is more simple to make corelation with debug trace...
and with proprietary module like websphere and weblogic can be deficulte to make good filter in strace/ltrace to debug...
and some is only to debug configuration probleme... not only bug...
Regards,
Mathieu
From: Ruediger Pluem [mailto:[EMAIL PROTECTED]
To: [email protected]
Sent: Sun, 18 Jun 2006 15:03:59 +0200
Subject: Re: [EMAIL PROTECTED] Re: debug apache
On 06/18/2006 02:49 PM, Mathieu CARBONNEAUX wrote:
> i think is very usefull to have this in production environment... to debug probleme without interupting production... in only up the log level with reload...
> with strace you must restart apache with strace...and for desactivating it you must restart... in some production environement is not acceptable...
Why that? You can attach strace to running processes, provided that you have appropriate permissions on this process. So
you might need root access for this.
Of course I admit that the strace / ltrace output is generic and a more specific output by logging inside the hooks
could provide better information.
Regards
Rüdiger
