| Current Path : /proc/2/cwd/usr/share/doc/dovecot-2.3.10.1/wiki/ |
| Current File : //proc/2/cwd/usr/share/doc/dovecot-2.3.10.1/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)
Copyright 2K16 - 2K18 Indonesian Hacker Rulez
;?>)