There is already a template built into config_parse.pl. That is how
default *.config files are built when one does not already exist for
a new mailing list.
In your situation, you need to find out "what" the cobalt server is
doing "exactly", and why it is doing it.
Every list is independent of each other and can be configured and
modified by the list-owner remotely. Using defaults or templates
is not a good idea for managing config files that may have been
tweaked by its owner.
You "could" set the permissions on the *.config files to 600, but if
the cobalt server does it's damage as root, all you can do is fix the
problem at the cobalt server rather than trying to react to the problem
at the majordomo server.
Dan Liston
"Martin.Eriksson" wrote:
>
> We running a cobalt server an everytime we update the cobalt server
> it patches something to majordomo. After that the *.config files is
> replaced.
> We have edited those files with a couple of lines. What to do for those
> files
> so that are not replaced or can you create a template file for those files?
>
> /Martin Eriksson
References:
|
|
