uawdijnntqw1x1x1
IP : 216.73.216.155
Hostname : vm5018.vps.agava.net
Kernel : Linux vm5018.vps.agava.net 3.10.0-1127.8.2.vz7.151.14 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64
Disable Function : None :)
OS : Linux
PATH:
/
var
/
..
/
usr
/
share
/
doc
/
.
/
dovecot-common
/
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 2010-05-24 04:42)
/var/../usr/share/doc/./dovecot-common/wiki/Debugging.ProcessTracing.txt