I'd like to use "config_list" to transfer list ALPHA's configuration to a new list BETA. Is this the recommended procedure?
bin/config_list -o config.ALPHA ALPHA
cp config.ALPHA config.BETA
Use an editor to change all occurrences of "ALPHA" in "config.BETA" to "BETA"
bin/newlist BETA
bin/config_list -i config.BETA BETA
Thanks for your ideas,
-- Prof Kenneth H Jacker khj@cs.appstate.edu Computer Science Dept www.cs.appstate.edu/~khj Appalachian State Univ Boone, NC 28608 USA
On Tue, Dec 26, 2000 at 02:11:25PM -0500, Kenneth Jacker wrote:
I'd like to use "config_list" to transfer list ALPHA's configuration to a new list BETA. Is this the recommended procedure?
bin/config_list -o config.ALPHA ALPHA
cp config.ALPHA config.BETA
Use an editor to change all occurrences of "ALPHA" in "config.BETA" to "BETA"
bin/newlist BETA
bin/config_list -i config.BETA BETA
You will lose your list membership if you do that.
The procedure is:
- rename the archive dirs and files
- rename list/alpha in list/beta
- ~mailman/bin/move_list beta
(or something close to this, I'm not online right now)
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
"MM" == Marc MERLIN <marc_news@valinux.com> writes:
On Tue, Dec 26, 2000 at 02:11:25PM -0500, Kenneth Jacker wrote:
I'd like to use "config_list" to transfer list ALPHA's configuration to a new list BETA. Is this the recommended procedure?
bin/config_list -o config.ALPHA ALPHA
cp config.ALPHA config.BETA
Use an editor to change all occurrences of "ALPHA" in "config.BETA" to "BETA"
bin/newlist BETA
bin/config_list -i config.BETA BETA
MM> You will lose your list membership if you do that.You shouldn't, since the list attributes containing membership information aren't dumped by config_list -o.
Remember one interesting thing about config_list that I think most people are not aware of: you can dump a list's configuration with config_list -o, then edit the resulting file, removing any configuration variables that you don't want to change. When you suck the edited file back into the list with config_list -i, only the listed variables will be changed.
You could use this, e.g. to change the web_page_url value for all your lists. Just create a file that contains
-------------------- snip snip -------------------- web_page_url = 'http://mynew.site.com/mailman/' -------------------- snip snip --------------------
and then config_list -i this into all your lists using a shell loop. Viola! All other list configuration variables will stay unchanged.
-Barry
On Tue, Jan 02, 2001 at 05:56:41PM -0500, Barry A. Warsaw wrote:
"MM" == Marc MERLIN <marc_news@valinux.com> writes:
On Tue, Dec 26, 2000 at 02:11:25PM -0500, Kenneth Jacker wrote:
I'd like to use "config_list" to transfer list ALPHA's configuration to a new list BETA. Is this the recommended procedure?
bin/config_list -o config.ALPHA ALPHA
cp config.ALPHA config.BETA
Use an editor to change all occurrences of "ALPHA" in "config.BETA" to "BETA"
bin/newlist BETA
bin/config_list -i config.BETA BETA
MM> You will lose your list membership if you do that.You shouldn't, since the list attributes containing membership information aren't dumped by config_list -o.
Note that he did a newlist BETA. If he had done cp lists/ALPHA/config.db lists/BETA/config.db, and then a move_list BETA, that would have kept the list membership, but a newlist BETA creates an empty list, and even though he's going to copy all the attributes, it's still going to be empty afterwards.
All that said, it doesn't matter because he didn't want to copy the membership.
Remember one interesting thing about config_list that I think most people are not aware of: you can dump a list's configuration with config_list -o, then edit the resulting file, removing any configuration variables that you don't want to change. When you suck the edited file back into the list with config_list -i, only the listed variables will be changed.
Yeah, that's very useful, I've used it more than once.
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
"MM" == Marc MERLIN <marc_news@valinux.com> writes:
MM> Note that he did a newlist BETA. If he had done cp
MM> lists/ALPHA/config.db lists/BETA/config.db, and then a
MM> move_list BETA, that would have kept the list membership, but
MM> a newlist BETA creates an empty list, and even though he's
MM> going to copy all the attributes, it's still going to be empty
MM> afterwards.
MM> All that said, it doesn't matter because he didn't want to
MM> copy the membership.You're right. Sorry, I misread the original message.
-Barry
participants (3)
-
barry＠digicool.com -
Kenneth Jacker -
Marc MERLIN