The BEST place to look for this kind of information is in the archives of
this list (majordomo-users) which are available on greatcircle.com, and
other locations which even provide search mechanisms.
In the majordomo.cf file (/etc?) you need to define your digest_work
directory, and this must have proper majordomo ownerships and permissions.
In order for digests to work, you also need to have an archive directory
for the completed digest to be stored in before it is mailed to your list
of digest subscribers.
Since your digests do get created, and they get sent out when the byte
count is exceeded, you probably have a good configuration. In order to
force these digests out daily, weekly, etc. requires a cron entry that
fires a message to majordomo forcing the digest to be created from files
in the work directory and sent to your list.
Examine the list-owner-info file in your docs directory, or search the
archives, but I do not currently have access to machines that I might
provide an example from.
Dan Liston
bitter1@absinthe.nu wrote:
>
> Hello; I have a Red Hat Linux 6.2 server and am trying to finish my setup
> of Majordomo 1.94.5. I am new to Linux and its cousins, having been a
> Macintosh person for many years. Apologies if my problem betrays my
> relative inexperience, but I have gone through the FAQ, and through at
> least three books with sections on majordomo... and have nearly given up
> in frustration.
>
> Everything is working except timed digests. They never ever send out.
> Oddly enough, digests which are sent out after a quantity of text is
> accumulated appear to work fine.
>
> I am perplexed. I've fiddled with cron. I've tried altering various
> options on the main and digest configuration file. I've tried every
> imaginable variation of digest aliases.
>
> I suspect three oddities might give a clue.
>
> The "mkdigest [listname] [password]" command does not give an error, but
> does not send out the digest either.
>
> When I attempt to run the "digest" script from the shell I get the
> following error: "Can't locate config_parse.pl in @INC (@INC contains: /
> usr/lib/perl5/5.00503/i386
> -linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /
> usr/lib
> /perl5/site_perl/5.005 .) at digest line 413." However, config_parse.pl
> is right there in the defined Majordomo home directory.
>
> When I attempt to run the "digest.send" script in the Tools subdirectory,
> it gives me this "digest.send: cd: /usr/spool/digests: No such file or
> directory". This directory in fact does not exist, but it was not created
> during the Majordomo installation... and I do not see where it is
> specified in any installation or configuration component. I wonder if it
> is trying to reach the working directory for the digests, which was
> defined at a different location. If so, I am confused why this script
> does not "know" it's looking in the wrong place.
>
> Any assistance onlist or offlist would be eternally appreciated. Thank you.
References:
|
|
