In MM 2.1, running bin/arch on a largish mbox file (~450MB) takes a
heck of a long time (~8 hrs) on a reasonably fast machine. The real
time eater seems to lie in generating the article database. Anyone
else run into this? Anyone have a solution?
--
Andrew Clark
Campus Network Programmer
Off
Is there any way (or if not, can there be a way) to limit the size/age
of an archive? The current method seems to be manual munging of the
mbox and then rerunning bin/arch.
--
Andrew Clark
Campus Network Programmer
Office of Information Technology
University of California, Santa Barbara
[EMAIL
October 25, 2002 16:15:06 -0400 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
"ADC" == Andrew D Clark <[EMAIL PROTECTED]> writes:
ADC> Since I'm hopelessly backlogged in my archive queue (1644
ADC> files), does anyone have any suggestions for spee
Since I'm hopelessly backlogged in my archive queue (1644 files), does
anyone have any suggestions for speeding up archiving? The qrunner process
is certainly eating up CPU and memory, but is only archiving about 1 msg
per minute. All the other queues move at a decent pace.
--
Andrew Clark
Ca
OK, so mailman 2.1b3 was doing a better of not getting backlogged than
mailman 2.0.12, but today I have 1085 files total in all the queues (552 in
the in queue). The oldest file in the in queue is about 1 hour old.
Should mailman be able to handle high volume bursty postings like this?
The sys
of California, Santa Barbara
[EMAIL PROTECTED] (805) 893-5311
--On Saturday, October 19, 2002 21:55:35 -0400 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
"ADC" == Andrew D Clark <[EMAIL PROTECTED]> writes:
ADC> I'm pretty sure lag in archiving is wh
tasks for one particularly high volume list were impacting
performance for other lists.
--
Andrew Clark
Campus Network Programmer
Office of Information Technology
University of California, Santa Barbara
[EMAIL PROTECTED] (805) 893-5311
--On Thursday, October 17, 2002 11:17:16 -0700 "Andre
I recently upgraded from mailman 2.0.12 to 2.1b3 and am quite pleased with
the new qrunner setup (among other things). We have one particularly high
volume list with very bursty postings (since the main poster is scripting
postings). In mailman 2.0.12 we'd often have hundreds of files stuck in
A better/easier fix might be to run httpd as the same user that you were
running it as under 1.3.24. Sounds like you were running it as GID 1
(daemon) before and are now running it as gid 60001.
--
Andrew Clark
Campus Network Programmer
Office of Information Technology
University of Californi
This one is always fun.
You can rerun ./configure and set the --with-cgi-gid to what it should be
(probably 60001 in your case), then rerun make (don't need to do make
install), then copy the newly compiled cgi wrapper over the old one.
--
Andrew Clark
Campus Network Programmer
Office of Inform
Same problems for me, and I am running a caching-only named on the box,
with Exim.
The only item in my qrunner log other than complaining about not being able
to acquire a lock is newsyslog turning the log file over...
Has anyone had luck in solving this problem through tuning the qrunner
varia
I've had consistent problems with the mailman qfiles directory getting
heavily backlogged (100-200 files stuck, sometimes for several hours) with
several various 2.0.x versions of mailman. The qrunner log shows lines
like so:
Oct 08 10:03:01 2002 (92546) Could not acquire qrunner lock
Oct 08
12 matches
Mail list logo
