In message <9405260005.AA28647@saimiri.primate.wisc.edu>, Software Development
writes:
> I have two lists, a non-digest version xxx and an accompanying digest
> version xxx-digest.
>
> For the non-digested list, I create an archive by explicitly listing
> archive2.pl as one of the "recipients".
>
> The the digested list, I do *not* want to create an archive (it would
> be redundant, given that there are already archive files for the xxx
> list. But how do I suppress archive creation for xxx-digest? It
> appears that the digest program wants to generate the digest file in an
> archive directory, and fails with an error if there is no such
> directory.
Use cron to delete the archives. Yes, it is a bug. It comes from the
way that digests creates its digest. It looks at all files in the
digest directory, not just files that match
[0-9][0-9][0-9]. Consequently there had to be some location to build
the digest that was going out that was seperate from the digest spool
directory. This is the archive directory. I added the patch to ignore
and complain about files in the digest directory that didn't match the
three digit format above, but I didn't make the changes to remove the
need for the archive directory.
Jerry Peek pointed this bug out to me when he was writing the 1.90
version of the majordomo chapter for his book. This bug is listed in
the README as item 28 in section 5.1.1. I don't have a timetable on
fixing it however.
-- John
John Rouillard
Senior Systems Consultant (SERL Project) University of Massachusetts at Boston
rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480
==============================================================================
My employers don't acknowledge my existence much less my opinions.
References:
|
|
