Bill Polhemus wrote:
>
> Well, I've done all I can think to do, and digesting/archiving still do not work. The thing is, I'm unsure as to how to "test"
> these. If I could tweak them, and then run some sort of test script, maybe I could debug and isolate.
>
> As it is, I fiddle, then wait till CRON runs to see if it worked. Damn sloppy.
>
> Any suggestions.
I really do not understand what is to test for archiving. Either the
file is created, and appended to with each message, or it isn't. As for
digests, you can send the "mkdigest listname-digest
listname-digest-outgoing password" message to majordomo any time you
want to force a digest to be created, regardless of size, lines, or age
of work files. If you only want to know if digestification processing
has begun, either work files will or will not exist after each message
to the list. This is explained in the list-owner-info file. From the
tar.gz install, this will be in your Doc directory. From an RPM
install, look in /usr/doc/majordomo-1.94.5.
If your aliases, listname(-digest).config files, and majordomo
ownerships and permissions on files and directories are correct, you
only need to look in the directories defined for $listdir,
$digest_work_dir, $filedir, and $filedir_suffix in your majordomo.cf for
the existance of properly named files after a message has been
received/distributed for the list in question.
If you are only supporting archiving (as required by digest), and
running a redhat RPM install, the directory to look in for work files
(by default) is /var/lib/majordomo/digest/listname-digest, and the end
result after a successful distribution of the digest is
/var/lib/majordomo/lists/listname-digest.archive/v01.n001. Just check to
see if the file has content matching the distributed message. The
filename is indicated by volume number and issue number of the digest.
Since the file is in a directory named for the list's digest, you know
what is digested before even seeing the volume and issue numbered files.
Dan Liston
Follow-Ups:
References:
|
|
