Hi,
I would much appreciate if someone could take the time to replicate the
following mailman behaviour.
Please let me know if you find the same issues.
Thanks in advance,
Regards,
Max
Max Lanfranconi wrote:
Mailman 2.1.11
Python 2.4.4
OS Solaris 2.11
Hi,
I have been able to
Max Lanfranconi [EMAIL PROTECTED] wrote:
Mailman 2.1.11
Python 2.4.4
OS Solaris 2.11
Hi,
I have been able to reproduce this bug consistently by running the
replicate_bug script:
replicate _bug is the following:
#!/bin/sh
/usr/local/mailman/bin/rmlist testlist1
/usr/local/mailman/bin/rmlist
Barry Finkel wrote:
Max Lanfranconi [EMAIL PROTECTED] wrote:
Mailman 2.1.11
Python 2.4.4
OS Solaris 2.11
Hi,
I have been able to reproduce this bug consistently by running the
replicate_bug script:
snip
I ran the script (after some minor modifications) on
Ubuntu Dapper
Mailman
Mark Sapiro wrote:
However, locking (at least list locking at the Mailman level) doesn't
seem to be involved in this case because each command process will
have saved and unlocked the list and terminated before the next
command process begins.
While is correct as far as it goes, I forgot about
This thread moved to Mailman-Developers. See
http://mail.python.org/pipermail/mailman-developers/2008-August/020330.html
for the analysis.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Mailman 2.1.11
Python 2.4.4
OS Solaris 2.11
Hi,
I have been able to reproduce this bug consistently by running the
replicate_bug script:
replicate _bug is the following:
#!/bin/sh
/usr/local/mailman/bin/rmlist testlist1
/usr/local/mailman/bin/rmlist testlist2
/usr/local/mailman/bin/rmlist
