Most everything is busted
Add this error to the pot: """ http://www.python.org/cgi-bin/moinmoin Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /cgi-bin/moinmoin. Reason: Document contains no data ------------------------------------------------------------------- Apache/1.3.9 Server at www.python.org Port 80 """ Also, as far as I can tell: + news->mail for c.l.py hasn't delivered anything for well over 24 hours. + No mail to Python-Dev has showed up in the archives (let alone been delivered) since Fri, 29 Dec 2000 16:42:44 +0200 (IST). + The other Python mailing lists appear equally dead. time-for-a-new-year!-ly y'rs - tim
"TP" == Tim Peters <tim.one@home.com> writes:
TP> + news->mail for c.l.py hasn't delivered anything for well TP> over 24 hours. TP> + No mail to Python-Dev has showed up in the archives (let TP> alone been delivered) since Fri, 29 Dec 2000 16:42:44 +0200 TP> (IST). TP> + The other Python mailing lists appear equally dead. There's a stupid, stupid bug in Mailman 2.0, which I've just fixed and (hopefully) unjammed things on the Mailman end[1]. We're still probably subject to the Postfix delays unfortunately; I think those are DNS related, and I've gotten a few other reports of DNS oddities, which I've forwarded off to the DC sysadmins. I don't think that particular problem will be fixed until after the New Year. relax-and-enjoy-the-quiet-ly y'rs, -Barry [1] For those who care: there's a resource throttle in qrunner which limits the number of files any single qrunner process will handle. qrunner does a listdir() on the qfiles directory and ignores any .msg file it finds (it only does the bulk of the processing on the corresponding .db files). But it performs the throttle check on every file in listdir() so depending on the order that listdir() returns and the number of files in the qfiles directory, the throttle check might get triggered before any .db file is seen. Wedge city. This is serious enough to warrant a Mailman 2.0.1 release, probably mid-next week.
[Barry A. Warsaw]
There's a stupid, stupid bug in Mailman 2.0, which I've just fixed and (hopefully) unjammed things on the Mailman end[1]. We're still probably subject to the Postfix delays unfortunately; I think those are DNS related, and I've gotten a few other reports of DNS oddities, which I've forwarded off to the DC sysadmins. I don't think that particular problem will be fixed until after the New Year.
relax-and-enjoy-the-quiet-ly y'rs,
I would have, except you appear to have ruined it: hundreds of msgs disgorged overnight and into the afternoon. And echoes of email to c.l.py now routinely come back in minutes instead of days. Overall, ya, I liked it better when it was broken -- jerk <wink>. typical-user-ly y'rs - tim
participants (2)
-
barry＠wooz.org -
Tim Peters