On Monday 18 April 2005 12:11 pm, Dan D Niles wrote:
> Larry Rosenman writes:
> > On Monday 18 April 2005 02:10 am, Jim Tittsler wrote:
> > > On Apr 15, 2005, at 12:22, Larry Rosenman wrote:
> > > > I have 178MEG of bounce-events-* files in my /data directory.
> > > >
> > > > Should these file
Larry Rosenman writes:
> On Monday 18 April 2005 02:10 am, Jim Tittsler wrote:
> > On Apr 15, 2005, at 12:22, Larry Rosenman wrote:
> > > I have 178MEG of bounce-events-* files in my /data directory.
> > >
> > > Should these files be hanging around?
> >
> > No. It sounds like either:
> >
On Monday 18 April 2005 02:10 am, Jim Tittsler wrote:
> On Apr 15, 2005, at 12:22, Larry Rosenman wrote:
> > I have 178MEG of bounce-events-* files in my /data directory.
> >
> > Should these files be hanging around?
>
> No. It sounds like either:
> - your bounce queue runner isn't running
It h
On Apr 15, 2005, at 12:22, Larry Rosenman wrote:
I have 178MEG of bounce-events-* files in my /data directory.
Should these files be hanging around?
No. It sounds like either:
- your bounce queue runner isn't running
- you've set REGISTER_BOUNCES_EVERY very large, so it hasn't processed
the acc
I have 178MEG of bounce-events-* files in my /data directory.
Should these files be hanging around?
I did have the Python 2.4* problem with strftime, but that is now fixed by
A local patch.
If these files need to be processed somehow, how?
Do they need to hang around?
Thanks!
--
Larry Rose
