[Mailman-Users] Upgrade to 2.0.3... now *everything* locks

[Ray Everett-Church]

Sorry to answer my own question, but one list in particular seemed to
have been screwed up... luckily it was a testing list. So I removed it,
deleted the lock files, and then did: make clean, ./configure, make
install, and make update yet again seems to have done the charm... it
even dislodged some things that must have been queued.

Could I suggest that someone provide more info somewhere (FAQ?) about
how lists might get locked up and how to free them without rmlisting
them?

Thanks...

> -----Original Message-----
> From: mailman-users-admin at python.org
> [mailto:mailman-users-admin at python.org]On Behalf Of Ray Everett-Church
> Sent: Thursday, March 15, 2001 8:03 PM
> To: mailman-users at python.org
> Subject: [Mailman-Users] Upgrade to 2.0.3... now *everything* locks
>
>
> Fairly recently upgraded to 2.0.1, and just upgraded to 2.0.3...
> Everything seemed fine, but upon the upgrade, every message I send
> produces a lock in the $path/locks that goes stale... the process that
> spawned it is long gone... and the messages never get delivered.
>
> What could be locking everything?
>
> Thanks,
> -Ray
>
>
> ------------------------------------------------------
> Mailman-Users maillist  -  Mailman-Users at python.org
> http://mail.python.org/mailman/listinfo/mailman-users
>