Software: Apache/2.2.22 (Debian). PHP/5.6.36 

uname -a: Linux h05.hvosting.ua 4.9.110-amd64 #3 SMP Sun Nov 4 16:27:09 UTC 2018 x86_64 

uid=1389(h33678) gid=1099(h33678) groups=1099(h33678),502(mgrsecure) 

Safe-mode: OFF (not secure)

/usr/share/doc/dovecot-core/wiki/   drwxr-xr-x
Free 1.48 GB of 7.22 GB (20.44%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     Debugging.ProcessTracing.txt (1.32 KB)      -rw-r--r--

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 2013-11-24 04:42)