[Mimedefang] Multiplexor dies, leaving its slaves clueless behind...

[Cormack, Ken]

> Signal 11 (Segfault) is nearly always a Program bug (Accessing memory that
is 
> not allocated to the current process, frequently address zero, usually 
> related to a pointer being used that has not been set correctly).   It is,

> nearly, impossible that it points to a hardware (memory, overclocking,
etc.) 
> problem.

I'm not saying a sig-11 isnt pointer, or other programming-related.  I'm
just saying that I used to see a ton of them, back in the days when I was
pushing an AMD 1700+ to it's overclocking limits.  I used to see how long it
would take to recompile the linux kernel, each time I would tweak the clock
settings.  (A poor-man's benchmark, yes.  But one that worked for me
::grin::).  When doing so, I made no changes to the kernel, the "make"
script, or anything else in the kernel compile proceedure, yet when I was
pushing the CPU too fast, I saw many Signal 11's.

Ken