In message <199310271829.AA02312@atlantis.eng.umd.edu>, "Randall S. Winchester"
writes:
>
> [yet again the question of what to do with the files explosion occurs]
GET AND READ THE ARCHIVES. Alan, Brent, Jenniffer and I have been
around and around with this, and the same question and an number of
answers were posted less than a week ago.
The answer is we are working on it. We are not sure exactly when the
config file will be here. I was up till 3AM this morning trying to get
all of my changes straightened out and working right before I leave
for LISA, so I can do a decent dog and pony show.
I personally would like to see it early Q1 of 94, but if things go
well, we may be able to get someting out before that. For now just
persevere because chances are that any changes you make will be
totally clobbered by the changes we make. In fact these changes that
Alan and I have proposed may be radical enough to require Majordomo
2.0. In fact, you might have to restructure your mailing list files
if we don't provide backward compatibility for the .auto, .xxx files.
When it does come, there will be three (maybe 4) files per mailing
list.
listname,
listname.config,
listname.passwd,
[listname.info]
My preference is to fold listname.info into the config file with a
info << EOF
This is the info for this list
EOF
style of multiline document. Technically listname.passwd could also be
done away with since there is equivalent functionality in the config
file, but for safety's sake a "trapdoor" password will be kept in the
listname.passwd file, that would work in the case that a bogus config
file made it through the sanity checks. Also it is likely that the
password will change more often than most other parameters, so a fast
way of changing it would be useful.
Now for a question:
How often to people change the listname.x files? Once a day, once a
week, once a month ... I am interested in changes to the following groups:
subscription policy files .auto, .closed
info file .info
ancillary files strip file .strip, hidden file .hidden, or .domain
password file .passwd
approval password (if in a file)
Note the approval password and admin password are seperate because
there may be more moderators than actual administrators of the list
due to the workload associated with moderating a busy list.
Also to the person who (sorry I lost the email, mailer driving error
at 2:30 ish) suggested that old config files should be automatically
checked into rcs before being supplanted, nice idea, but that would
need a mechanism to pull a particular revision of the file out to be
useful, so I don't think so. but I think all of the hooks would be
there to make an addon module do it.
-- John
John Rouillard
Special Projects Volunteer University of Massachusetts at Boston
rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480
Consulting Systems Programmer Bose (until 10/29/93)
rouilj@bose.com Framingham, MA (508) 879-1916 x6483
===============================================================================
My employers don't acknowledge my existence much less my opinions.
Follow-Ups:
References:
|
|
