I do not use wilma, so will have to let someone else attack that answer
for you, but for archiving in general, you have more than just aliases
to deal with. You have to make sure the $filedir and $filedir_suffix
are set correctly (corresponding to your aliases or vice versa).
It looks like you have managed to combine both archive storage
schemes into one alias. Assuming (and you know what assuming
does) you have $filedir = "/var/lib/majordomo/archives"; in the
majordomo.cf, and $filedir_suffix = "";, then your alias
test-archive: "|/usr/lib/majordomo/wrapper archive2.pl
-f /var/lib/majordomo/archives/test.archive/test
-a -m"
would create a file called
/var/lib/majordomo/archives/test.archive/test.0201
for this month, which really goes beyond what you need or
probably even intended. With the same majordomo.cf setting
above, I would create my alias for test-archive to look like
test-archive: "|/usr/lib/majordomo/wrapper archive2.pl
-f /var/lib/majordomo/archives/test/test -a -M"
Each list gets it's own archiving directory, and the final
FQDN listed in the -f argument is a filename, then that
becomes the basename with an extension of .MMYYYY for -M
or .MMYY for -m. If the FQDN only points to a directory,
with no basename specified, the filenames in the directory
become just MMYY or MMYYYY filenames.
Using wilma may have it's own requirements, but I suggest
experimenting with the alias above to meet your requirements
first.
Dan Liston
"TOTK.com Sports" wrote:
>
> Hello,
>
> I want to set up archives of my lists on v1.94.4 on RedHat 6.1
>
> I made a file called test in /var/lib/majordomo/archives/test.archive, owned
> by majordomo and added this to /etc/aliases:
>
> test-archive: "|/usr/lib/majordomo/wrapper archive2.pl
> -f /var/lib/majordomo/archives/test.archive/test
> -m -a"
>
> What else do I do?
>
> Also, how difficult is Wilma to implement?
>
> Thanks in advance for any help!
> ----------
> -Ralph
|
|
