[Mailman-Developers] Running Solaris 8 on Intel platform with i810 chipset

2001-05-03 Thread Marco Paludo
Hello to All, Is there a XServer to have Solaris 8 Intel platform edition running properly with the Intel 82810 chipset? As much as know, XFree86 release 4.0.3 only supports the i810 chipset for the Linux operating system. Is there a technical reason, why this hardware is not supported for the S

[Mailman-Developers] Patch to add class Img to htmlformat.py

2001-05-03 Thread Ben Burnett
I don't know if anyone else will find this usefull, but here goes. - Ben PS I used it to add a logo to the top of some of the web interface pages for example in listinfo.py -- def FormatListinfoOverview(error=None): "Present a general welcome and itemize the (public) lists for this host

Re: [Mailman-Developers] Re: [Mailman-Users] Big problems with stale lockfiles on large list...

2001-05-03 Thread Barry A. Warsaw
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> I think this code isn't quite right. I think to be totally BAW> safe, you want sigterm_handler() to sys.exit(0) after the BAW> call to mlist.Unlock(). Otherwise, depending on race BAW> conditions, after unlocking th

Re: [Mailman-Developers] Re: [Mailman-Users] Big problems with stale lockfiles on large list...

2001-05-03 Thread Barry A. Warsaw
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> So the code in admin.py looks something like: | def main(): | ... | mlist = MailList.MailList(listname, lock=0) | ... | | def sigterm_handler(signum, frame, mlist=mlist): | ml

[Mailman-Developers] Re: Big problems with stale lockfiles on large list...

2001-05-03 Thread Barry A. Warsaw
> "GT" == Graham TerMarsch <[EMAIL PROTECTED]> writes: GT> FWIW Barry, this patch appears to have just about completely GT> solved our lockfile problems and stalled WWW pages that we GT> were having. GT> I used to be able to use "ab" (ApacheBench) to pound on one of GT>

[Mailman-Developers] Re: Big problems with stale lockfiles on large list...

2001-05-03 Thread Graham TerMarsch
On Thursday 03 May 2001 01:14, Barry A. Warsaw wrote: > > "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: > > CVR> By the by, I hate to say this, but I think this thing > CVR> deserves a 2.0.5 subrelease > > Oh, let me add (since it's 4am :), that I also would like to get mor

Re: [Mailman-Developers] Re: Big problems with stale lockfiles on large list...

2001-05-03 Thread Graham TerMarsch
On Thursday 03 May 2001 01:13, Barry A. Warsaw wrote: > > "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: > >> Barry, wanted to thank you muchly for the lengthy description > >> of the problem and the patch that you provided. I figured that > >> this was probably what was ha

[Mailman-Developers] MHonArc integration

2001-05-03 Thread Anand Kumria
Hi folks, I've just setup another mailman site and once again I wanted to integrate it with MHonArc. Previously I'd been using shell script that played games with symlinks and the the archive files behind Mailman's back. I wanted something simpler to use, so after much judicious cutting and past

Re: [Mailman-Developers] Re: Big problems with stale lockfiles onlarge list...

2001-05-03 Thread Barry A. Warsaw
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: CVR> By the by, I hate to say this, but I think this thing CVR> deserves a 2.0.5 subrelease Oh, let me add (since it's 4am :), that I also would like to get more feedback on the success of the patch. One thing I don't want

Re: [Mailman-Developers] Re: Big problems with stale lockfiles onlarge list...

2001-05-03 Thread Barry A. Warsaw
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: >> Barry, wanted to thank you muchly for the lengthy description >> of the problem and the patch that you provided. I figured that >> this was probably what was happening, after having gone through >> the process of run

[Mailman-Developers] Re: Big problems with stale lockfiles on large list...

2001-05-03 Thread Barry A. Warsaw
> "GT" == Graham TerMarsch <[EMAIL PROTECTED]> writes: GT> Barry, wanted to thank you muchly for the lengthy description GT> of the problem and the patch that you provided. I figured GT> that this was probably what was happening, after having gone GT> through the process of