hi-

i think that someone posted earlier today regarding sporadic sig 11's on
freebsd 4.2-RELEASE while running qmail-qfilter.

interestingly, i just installed qmail-qfilter earlier today on the same
release of freebsd, and i'm getting the same thing:

Jun  4 19:46:03 mx1 /kernel: pid 64541 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 19:48:39 mx1 /kernel: pid 64670 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 20:01:07 mx1 /kernel: pid 65370 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 20:04:58 mx1 /kernel: pid 65495 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 20:18:38 mx1 /kernel: pid 66276 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 20:50:45 mx1 /kernel: pid 68131 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 21:02:07 mx1 /kernel: pid 68625 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 21:52:43 mx1 /kernel: pid 70813 (qmail-qfilter), uid 1003: exited
on signal 11
Jun  4 22:26:45 mx1 /kernel: pid 71658 (qmail-qfilter), uid 1003: exited
on signal 11

the previous thread on this topic ended when it was suggested that the
problem was running softlmit with a limit of 2 meg, which didn't give the
perl interpreter enough room to get started.  

interestingly enough, the problem persists after removing the softlimit
from /var/qmail/supervise/qmail-smtpd/run. (i'm running LWQ-style)

i've checked the sig 11 FAQ (www.bitwizard.nl/sig11), but that doesn't
seem to have anything relevant.

has anyone else running qmail on freebsd noticed this behavior?

thanks-

dan



Reply via email to