On Mon, Sep 21, 1998 at 11:02:50AM +1200, pete clare wrote:
> don't know if its the same thing but after going to 2.03 on a couple
> of freebsd boxes i'm getting this in my logs - never saw it prior to
> 2.03.
>
> Sep 21 01:36:54 t-car /kernel: pid 12602 (exim), uid 0: exited on signal 11
> Sep 21 04:00:39 t-car /kernel: pid 14557 (exim), uid 0: exited on signal 11
> Sep 21 06:14:22 t-car /kernel: pid 16280 (exim), uid 0: exited on signal 11
> Sep 21 08:31:44 t-car /kernel: pid 18090 (exim), uid 0: exited on signal 11
>
> the original exim process is still running and mail seems to be coming in
> fine.
It appears I've got the same thing in my logs (on 2.03) (FreeBSD 2.27
machine):
Sep 15 20:27:38 orac /kernel: pid 21764 (exim), uid 40: exited on signal 11
Sep 16 00:12:30 orac /kernel: pid 26013 (exim), uid 40: exited on signal 11
Sep 16 10:48:45 orac /kernel: pid 8376 (exim), uid 40: exited on signal 11
Sep 16 17:00:28 orac /kernel: pid 15318 (exim), uid 40: exited on signal 11
Sep 18 03:45:56 orac /kernel: pid 25360 (exim), uid 40: exited on signal 11
Sep 19 06:54:27 orac /kernel: pid 2008 (exim), uid 40: exited on signal 11
I can also tie in every single one of these with a message coming in
shortly after via my backup mx relay...
Regards, Matthew
--
Matthew Frost http://www.frost.org/
email: matthew@???
"My feet, my arms and my ears. And, your feet." dfax: +44 870 160 0853
--
*** Exim information can be found at
http://www.exim.org/ ***
