> Here's how my digests are set up:
>
> Suppose a list foobar and it's digest foobar-digest.
> The subscriber lists for these files are in ~majordomo/lists
> as defined in majordomo.cf.
Got that and it works.
> The working directory for the digest is ~majordomo/digest as
> defined in majordomo.cf.
Check.
> In the directory ~majordomo/digest there will be a subdirectory
> called foobar-digest. This is where the messages are collected
> throughout the day.
Check again.
> When I use the mkdigest command and I give it
> the list name foobar-digest it looks in the digest_work_dir for
> the messages to create and then sends it out to the foobar-digest
> list.
Hold it. When I send mkdigest test-digest <pass> I get a no list
error returned. The digest never gets created.
> Finally the resulting digests are kept in ~majordomo/lists/
> foobar-digest.archive (a directory). These digests are subsequently
> moved to an ANON FTP server for retrieval by people wanting old
> list traffic.
>
> Hope that helps.
>
> Mike
>
I'm golden up until the mkdigest command. Then things crash and
burn. Maybe I'm missing a symptom in that mkdigest test-digest fails
and the problem is really earlier that where I think?
----------------------------------------------------------------------------
Chris Johnson Internet: johnson@chaos.dac.neu.edu
Assistant Director, Systems BITNET: johnson@nuhub
Division of Academic Computing Voice: 617.373.3300
Northeastern University, 39 RI FAX: 617.373.8600
360 Huntington Ave.
Boston, MA., U.S.A. 02115
----------------------------------------------------------------------------
|
|
