b
Jul 20 16:42:32 mupdate-dev master[18240]: about to exec
/usr/cyrus/bin/mupdate
Jul 20 16:42:32 mupdate-dev master[18234]: process 18239 exited,
signaled to death by 6
Jul 20 16:42:32 mupdate-dev master[18234]: process 18240 exited,
signaled to death by 6
Jul 20 16:42:32 mupdate-dev master[18
op) to hang.
This is consistent with a lock being held in the Berkeley db
environment when a process crashes.
On examining the logs, I found that each of these incidents was
immediately preceded by the message:
"signaled to death by 6"
4 times the process in question was im
. From this
it appears that when a process is aborted in this fashion, some resource is
remaining locked causing all new processes (lmtpd, imapd and pop) to hang.
On examining the logs, I found that each of these incidents was immediately
preceded by the message:
"signaled to death by 6"
4
