On Thu, Feb 28, 2002 at 07:48:45PM +0000, Michael Johnson wrote:
> More importantly, how to prevent such things as future occurences.
> Certainly, manually checking and removing the lock may work on a per
> instance basis, but, in reality, it appears less than ideal. This problem
> happens way to frequently. Would changing the frequency depending the
> system of qrunner cron alleviate difficult locks? Is this a race condition
> issue with qrunner?
Unless you are having crashes (like a bad message crashing qrunner), in
which case, it should show up in your mailman logs (~mailman/logs/), qrunner
doesn't just casually die and leave a lock behind.
At least, it doesn't on my sites.
Marc
--
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger [EMAIL PROTECTED] for PGP key
------------------------------------------------------
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
