Mailing List Archive

POP3D SIGKILL
Hi Paul,



I'm loving 3.1.17, IMAPD is stable, in two days it's consuming 1.2GB of RAM,
LMTPD stable (my error was using too much instances, my fault), but so far
working great, just a few aparts that i'll take care in time like the
dbmail-util,



I'm using monit to take care of any problem just in case, and I'm seeing
that pop3d dies 2 or 3 times a day.

I was gdb'ing it, and it received a SIGKILL, but I don't have any script or
cron killing it.



It there a way to ignore the SIGKILL to that I can get a trace?

Can I just set: handle SIGKILL nostop



And will be able to get the trace?



[Thread 0xb6abcb40 (LWP 23250) exited]



Program terminated with signal SIGKILL, Killed.

The program no longer exists.

(gdb)

(gdb) bt full

No stack.

(gdb)