> > If the word "global" is the first word of the parameter, then an
> > administrator-defined set of files is also searched for any line
> > that matches the parameter.
> But the global command and its extentions should force a replacement
> of the standard do_lists command from a module, don't build this into
> majordomo proper, so those people who aren't interested in it don't
> have to deal with it as far as setup or anything.
Adding the code to search a few text files is a trivial addition,
and is not *worth* the bother of a replacement command or extra module.
If you want to have the extended lists available, put a list of file
names in some variable in majordomo.cf. Or don't bother if you don't
want to.
> With this
> distributed scheme each majordomo-master could poll the
> majordomo-servers list seperately. That does bring up a problem of
> keeping all of the lists synchronized though.
I was trying to avoid synchronizing anything. That brings up another
order of magnitude of complexity, which isn't being addressed in any
way by Majordomo currently.
> I think it will work fine, but I DO NOT want to see it in majordomo
> proper. Put it into an entirely seperate file that can be included
> from majordmo.cf, or via a module load command.
> (&module_load(module_dir) requires all files in that directory).
The option to the "lists" command to search an optional admin-
defined text file should be in the stock Majordomo release. The
rest of the stuff for creating consolidated lists from other
Majordomo's should definitely be separate.
- Alan
---- ,,,,
Alan Millar amillar@bolis.SF-Bay.org __oo \
System Administrator =___/
And Moses said, "Oh, Lord, please send someone else to do it!" -Exodus 4:13
|
|
