Great Circle Associates List-Managers
(December 2001)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: [list-managers] Digest delays
From: "Roger B.A. Klorese" <rogerk @ queernet . org>
Date: Mon, 24 Dec 2001 11:32:00 -0800
To: Nick Simicich <njs @ scifi . squawk . com>,list-managers @ greatcircle . com
In-reply-to: <5.1.0.14.2.20011224132634.05de9d58@127.0.0.1>
References: <5.1.0.14.0.20011223195500.04a8d5c8@gopostal.onlinepolicy.n et><75489484.1009102131@[192.168.0.4]><20011223132004.2D7A42CC5D@mycroft.greatcircle.com><20011223132004.2D7A42CC5D@mycroft.greatcircle.com>

At 01:27 PM 12/24/2001 -0500, Nick Simicich wrote:
>At 08:00 PM 2001-12-23 -0800, Roger B.A. Klorese wrote:
>
>>Configuring Mj2 digests is an arcane art, lemme tell ya.  There are so 
>>many things you can set -- maximum age of oldest post, minimum age of 
>>newest post, maximum size, minimum size, whether each permitted run 
>>generates a single digest or how many it takes to clear the queue, hours 
>>at which digests can be generated -- that one really has to work the 
>>combinations till one finds one that works for the list.
>
>This sounds like the definition of "broken" to me.

Well, you'd be wrong.

The multiple parameters give great flexibility, unlike Mj1 where you had a 
very limited set of options (age and size).  It would be nice if it were 
better documented so the interactions were a little more obvious, but I'm 
very happy to have the increased control and flexibility, and to have it in 
a way that doesn't require me to write crontabs.




References:
Indexed By Date Previous: Re: [list-managers] Digest delays
From: Charlie Summers <charlie@lofcom.com>
Next:
From: (nil)
Indexed By Thread Previous: Re: [list-managers] Digest delays
From: Charlie Summers <charlie@lofcom.com>
Next:
From: (nil)

Google
 
Search Internet Search www.greatcircle.com