Great Circle Associates Majordomo-Users
(April 2006)
 

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

Subject: Re: Indigestion
From: Daniel Liston <dliston @ sonny . org>
Date: Sat, 29 Apr 2006 13:37:01 -0500
To: Joe Hartley <jh @ brainiac . com>
Cc: majordomo-users @ greatcircle . com
In-reply-to: <20060429080711.6b17ed43.jh@brainiac.com>
References: <20060429080711.6b17ed43.jh@brainiac.com>

There is a simple cure for the indigestion problem you are experiencing.
This seems to be a recurring problem for you, as you asked a similar
question in May of 2000.  Did you do a fresh install of majordomo or
something? ;)

digest:
line 176 should be changed to say;
foreach (sort @files) {

Dan Liston

On Sat, 2006-04-29 at 08:07 -0400, Joe Hartley wrote:
> Hi, folks.  I've got some lists that I've been running with Majordomo for
> years on a number of different servers.  I've just migrated to a dual
> processor Sun running AuroraLinux 2.0 (based on Fedora Core 3), and I've
> run into a problem that's just got me stumped.
> 
> The regular lists work fine, but the digests are not.  My config files
> (which haven't changed in years) are set to spit out a digest once a day
> (or 40K lines, whichever comes first).
> 
> What has been happening though is that if I start with an empty digest
> work directory, the messages will build up for a day, and once a message
> comes that's 24 hours older than the oldest message in the directory, a
> digest is built with a seemingly random subset of the messages in the
> digest work directory.
> 
> Here's a listing of the work directory before the digest gets produced:
> [root@zappa tv-digest]# ls -l
> total 96
> -rw-rw----  1 majordomo majordomo 1553 Apr 27 21:37 001
> -rw-rw----  1 majordomo majordomo 1736 Apr 28 07:31 002
> -rw-rw----  1 majordomo majordomo 2072 Apr 28 08:47 003
> -rw-rw----  1 majordomo majordomo 1587 Apr 28 10:11 004
> -rw-rw----  1 majordomo majordomo 2073 Apr 28 10:21 005
> -rw-rw----  1 majordomo majordomo 2186 Apr 28 10:56 006
> -rw-rw----  1 majordomo majordomo 1692 Apr 28 11:14 007
> -rw-rw----  1 majordomo majordomo 1641 Apr 28 13:35 008
> -rw-rw----  1 majordomo majordomo 2427 Apr 28 14:11 009
> -rw-rw----  1 majordomo majordomo 1524 Apr 28 14:24 010
> -rw-rw----  1 majordomo majordomo 1722 Apr 28 14:54 011
> -rw-rw----  1 majordomo majordomo 1103 Apr 28 17:33 012
> 
> and here's one after:
> [root@zappa tv-digest]# ls -l
> total 64
> -rw-rw----  1 majordomo majordomo 1553 Apr 27 21:37 001
> -rw-rw----  1 majordomo majordomo 1736 Apr 28 07:31 002
> -rw-rw----  1 majordomo majordomo 2186 Apr 28 10:56 006
> -rw-rw----  1 majordomo majordomo 1692 Apr 28 11:14 007
> -rw-rw----  1 majordomo majordomo 2427 Apr 28 14:11 009
> -rw-rw----  1 majordomo majordomo 1524 Apr 28 14:24 010
> -rw-rw----  1 majordomo majordomo 1722 Apr 28 14:54 011
> -rw-rw----  1 majordomo majordomo 1103 Apr 28 17:33 012
> 
> A digest was produced with messages 3, 4, 5, and 8.  Why not the rest of
> them?
> 
> And after that point, each subsequent message will generate a new digest
> with just that new message.
> 
> Running 'wrapper config-test' indicates that everything's OK with 
> permissions and settings, and my config files have been the same for
> years now.
> 
> I'm really stumped by this sort of working.  Has anyone ever seen this
> sort of behavior?  
> 



Follow-Ups:
References:
Indexed By Date Previous: Indigestion
From: Joe Hartley <jh@brainiac.com>
Next: Re: Indigestion
From: Joe Hartley <jh@brainiac.com>
Indexed By Thread Previous: Indigestion
From: Joe Hartley <jh@brainiac.com>
Next: Re: Indigestion
From: Joe Hartley <jh@brainiac.com>