This error message means you have achieved the bytes, lines, or days
required by your .config file to compile the files located in your
$digest_work_dir/directors/ location into a digested message for
distribution. The digest utility depends on other variables and settings
in /etc/majordomo.cf OR the majordomo.cf pointed to by a -c argument on
the digestify alias.
Does /etc/majordomo.cf exist? Is it readable by the majordomo user?
Does the directory appear in any of your aliases? Particularly any with
-outgoing, -archiver, or -digestify?
Dan Liston
Robert Isaac wrote:
> I thought I had everything set up and was working OK, but just got this
> email from one of our lists:
>
> *MAJORDOMO ABORT (mj_digest)!!*
>
> *open(DIGEST,
> ">/usr/local/majordomo/lists/directors-digest.archive/v01.n001"):
> No such file or directory*
>
>
> I know there is no such directory or file as /directors-digest.archive
> was never set up.
>
> I set up as per Archive-Digest_HOW-TO_2-2.txt:
>
> mkdir /usr/local/majordomo/archives/directors
> mkdir /usr/local/majordomo/archives/directors-digest
> mkdir /usr/local/majordomo/digests/directors-digest
>
> ..so where has this path come from:
> */usr/local/majordomo/lists/directors-digest.archive/*
>
>
> In /majordomo.cf I have:
> $listdir = "$homedir/lists";
> $filedir = "$homedir/archives";
> $filedir_suffix = "";
> $digest_work_dir = "$homedir/digests";
>
> In /lists/directors.config and /lists/directors-digest.config I have:
> archive_dir = /usr/local/majordomo/archives/directors
> digest_archive = /usr/local/majordomo/archives/directors-digest
>
> Bob
>
> ___________________________________________________
> Robert Isaac
> Director and Web Administrator
> Volvo Owners Club
>
> _www.volvoclub.org.uk_ <file://www.volvoclub.org.uk>
>
> Please include all previous text with reply
> All messages are scanned with an antivirus scanner.
>
Follow-Ups:
References:
|
|
