===8<=== CUT ===>8===
> It took an email I sent 27 hours to return to me. Looking at
> the headers, it appears that vger sat on the email almost
> 90%(est) of the time. The vger setup may have the best exploder
> config in the world, but if the main machine isn't dolling them
> out fast enough, what is the point?
> I know this comes up every so often, and usually cvs is just
> turned off, until the queue has time to catch up. That doesn't
> fix the problem, tho. Cvs and these lists should not be on the
> same box. cvs should not be on a box with anything else(should
> cvs even be?).
Based on the messages I've been receiving relating to emails sent to
various vger lists, it looks like vger actually crashed - I received
several "mailserver does not answer" messages relating to vger, and
ping failed to produce any responses (it's currently showing around
100ms ping times).
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/