Great Circle Associates Majordomo-Users
(January 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Editing *.config files
From: bill @ biome . bio . dfo . ca (Bill Silvert)
Date: Thu, 23 Jan 1997 15:06:29 -0400 (AST)
To: majordomo-users @ GreatCircle . COM

Dave Wolfe writes:

>First off, are you really editing the <listname>.config directly? If so,
>stop it! Use the 'config' and 'newconfig' commands. Mj will tell you
>whether or not the config file parses correctly then.

I was kind of shocked to read this, since I always edit
<listname>.config directly and would find it inconvenient not to do so
(at least it seems this way to me, I have never bothered learning how to
to use the config command). Not all of the entries can be changed in
this way, and there are times when I want to modify the X-headers for
over 40 lists at a time or something like that.

So can Dave or someone else explain what is wrong with direct editing?
I realise that it can help to have Mj parse the command to check its
correctness, but if the manager is confident in the syntax of the
change, what is the danger?

-- 
Bill Silvert, Habitat Ecology Section, Bedford Institute of Oceanography,
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2, Tel. (902)426-1577


Follow-Ups:
Indexed By Date Previous: Re: Perl Problem
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Perl Problem
From: Bill <bill@wagill.com>
Indexed By Thread Previous: Re: Majordomo abort "do_exec_sendmail"
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Editing *.config files
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>

Google
 
Search Internet Search www.greatcircle.com