On Tuesday 20 November 2001 16:38, Jon Carnes wrote:
> I've seen this happen when the Admin has the database for a list locked
> while they make changes via the Web-interface. Once they log out and
> release their lock on the database then qrunner can access the list and
> send the waiting messag
sage -
From: "Dan Wilder" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 20, 2001 2:27 PM
Subject: Re: [Mailman-Users] qrunner locks are not always removed
> On Tue, Nov 20, 2001 at 10:49:08AM -0800, Harold Paulson wrote:
> >
> > >Nov
On Tue, Nov 20, 2001 at 10:49:08AM -0800, Harold Paulson wrote:
>
> >Nov 15 21:51:02 2001 (5617) Could not acquire qrunner lock
>
> This is probably normal behavior. qrunner starts up from cron once a
> minute. If there is a lock file laying around, it knows that an
> older qrunner is still
>Nov 15 21:51:02 2001 (5617) Could not acquire qrunner lock
This is probably normal behavior. qrunner starts up from cron once a
minute. If there is a lock file laying around, it knows that an
older qrunner is still active, and shuts itself down.
That being said, this message worried me too
arnes
- Original Message -
From: "Lucas Hofman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 20, 2001 3:43 AM
Subject: [Mailman-Users] qrunner locks are not always removed
> Nov 15 21:51:02 2001 (5617) Could not acquire qrunner lock
> Nov
Nov 15 21:51:02 2001 (5617) Could not acquire qrunner lock
Nov 15 21:52:01 2001 (5619) Could not acquire qrunner lock
Nov 15 21:53:02 2001 (5621) Could not acquire qrunner lock
Nov 15 21:54:02 2001 (5623) Could not acquire qrunner lock
Nov 15 21:55:03 2001 (5625) Could not acquire qrunner lock
Nov
