403Webshell
Server IP : 23.254.227.96  /  Your IP : 216.73.216.7
Web Server : Apache/2.4.62 (Unix) OpenSSL/1.1.1k
System : Linux hwsrv-1277026.hostwindsdns.com 4.18.0-477.13.1.el8_8.x86_64 #1 SMP Tue May 30 14:53:41 EDT 2023 x86_64
User : viralblo ( 1001)
PHP Version : 8.1.31
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/doc/dovecot/wiki/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/doc/dovecot/wiki/Debugging.ProcessTracing.txt
Process Tracing
===============

If a Dovecot's process hangs or is just really slow, the best way to debug it
is to see what it's really doing. Typically you'd be looking into imap or pop3
processes.

Linux
-----

---%<-------------------------------------------------------------------------
strace -tt -o log -p <process pid>
---%<-------------------------------------------------------------------------

BSDs, OS X <= 10.4
------------------

---%<-------------------------------------------------------------------------
# enable process tracing
ktrace -f log -p <process pid>
# do whatever makes it break, then stop the process tracing:
ktrace -C
# and see what it's done:
kdump -T -f log
---%<-------------------------------------------------------------------------

OS X >= 10.5
------------

---%<-------------------------------------------------------------------------
dtruss -p <process id>
---%<-------------------------------------------------------------------------

Solaris
-------

---%<-------------------------------------------------------------------------
truss -d -r0 -w1 -o log -p <process pid>
---%<-------------------------------------------------------------------------

'-r0' and '-w1' cause all IMAP input/output to be logged. '-d' adds timestamps
to the log.

(This file was created from the wiki on 2019-06-19 12:42)

Youez - 2016 - github.com/yon3zu
LinuXploit