X-PMC-CI-e-mail-id: 8020
Hello,
I am a user of majordomo 1-94.4, on SunOS 4.1.4 on Sparc 5, with Perl
"This is perl, version 5.004_01".
(Sorry, I am not a subscriber of the list, so if you could kindly
respond to my e-mail account I will appreciate it.
Does sending to majordomo-users-request get me subsdribed?)
I have been using majordomo to support a small mailing list of several
users. The installation went rather well. It was done early last year,
and the list has been working for about a year.
Lately, I was asked to change the setting of a few features, and I
used config to obtain the configuration file of the list in question
and then sent it back after modification by newconfig.
Well, for some strange reasons, the newconfig doesn't accept my new
configuration and reported back an error.
I recall that I used the config/newconfig in the past, the last time
probably last summer and it worked flawlessly.
After some experimentation this time, however, I found that the
newconfig even refuses to accept the UNMODIFIED config that it sent me
when I issued config. Further the error message suggests that
something is totally broken. But I am not sure what (maybe upgraded
perl?).
========================================
Bad RETURN example:
----------------------------------------
--
>>>> newconfig xyz xyzabc
The new config file for xyz was NOT accepted because:
close at line 379 is not a valid value.
Valid values are: open;closed;auto;open+confirm;closed+confirm;auto+confirm
>>>>
>>>>
>>>>
========================================
Ok, but what is this error message. There is no "close" designation in
the config.
Also the input at line 379 turns out to be who_acccess line and
this is assigned an "open" enum value. Very strange...
(I can see that it was updated last June using newconfig.?)
========================================
# who_access [enum] (open) <majordomo> /open;closed;list/
# One of three values: open, list, closed. Open allows anyone
# access to this command and closed completely disables the command
# for everyone. List allows only list members access, or if
# restrict_post is defined, only the addresses in those files are
# allowed access.
who_access = open
#[Last updated Fri Jun 6 23:02:19 1997]
========================================
Worse, if I removed the "open" from "= open" in the above,
now newconfig reports that the assignment in front of who_access,
namely that of which_access is now invalid because of "close" value!!!
I ran wrapper config-test for verification and it does not detect any
errors.
Has anyone encountered problem like this?
Is it possible that the upgrade of Perl (maybe a few times) since the
time majordomo was first installed broke something in the majordomo
code?
--
Ishikawa, Chiaki ishikawa@personal-media.co.jp.NoSpam or
(family name, given name) Chiaki.Ishikawa@personal-media.co.jp.NoSpam
Personal Media Corp. ** Remove .NoSpam at the end before use **
Shinagawa, Tokyo, Japan 142
Follow-Ups:
|
|
