Re: Digestion problem
Daniel Liston <[email protected]> Sat, 19 Dec 2009 22:30:29 -0600
| Newsgroups | gmane.mail.majordomo.general |
|---|---|
| Message-ID | <[email protected]> |
It took me awhile to find this gem, but please let me know if it helps in
your situation. In the digest file, please make this "diff" modification:
176c176
foreach (@files) {
---
foreach (sort @files) {
For any novices following this thread, the above means:
Change line 176 from the line before --- to match the line after it.
Short version, add the word/command "sort " before @files in parenthesis.
Dan Liston
Joe Hartley wrote:
> I've recently moved my majordomo lists to a new server running CentOS 5.4.
> Majordomo made the transition well enough, except for one problem that I
> am having with digests.
>
> The incoming messages are correctly written to the digest work directory,
> but when the digest is created, the first three files are routinely
> ignored, and the digest is built from messages 004 upward. After that,
> each message to the list is sent to the digest list individually,
> presumably because it's over a day older than the 001 message.
>
> Manually clearing the digest work directory doesn't fix the problem;
> the messages start getting written to the directory from 001 as expected,
> then behave as above.
>
> I migrated my server by rsyncing the /usr/local/majordomo and
> /usr/local/majordomo-work directories to the new server and recompiling
> wrapper. Overall it seems to be fine. The non-digest lists work as
> expected, it's just the digestion that is the issue. This is happening on
> both the lists I have digests for, though one is not terribly active so
> I don't know if its "breaking point" is the 003 message or not.
>
> Has anyone seen this behavior before? Does anyone know if there's a
> message counter variable stored somewhere that I don't know about that
> came over with the migration?
>
> Thanks in advance for any clues toward solving this issue.
>