Great Circle Associates Majordomo-Users
(May 1998)
 

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

Subject: Re: MajorCool (1.3.0) truncating restrict_post on modify
From: Bill Houle <Bill . Houle @ SanDiegoCA . NCR . COM>
Date: Mon, 18 May 1998 17:09:48 -0700
To: Richard Hopkins <Richard . Hopkins @ bristol . ac . uk>, Majordomo-Users @ GreatCircle . COM
In-reply-to: <SIMEON.9805181626.J@rjh.bris.ac.uk>

At 04:00 PM 5/18/98 +0100, Richard Hopkins wrote:
>MajorCool (version 1.3.0) seems to truncate long "restrict_post" values, 
>unexpectedly, when you use it to modify list configurations. (Only happens 
>if you actually modify restrict_post; no problems if you modify other 
>things.)
> 
>From a quick peek at the code, it looks to me like it should cater for 
>input of up to 128 characters, but it seems to truncate to something less 
>than 80 before writing out the config file. No warnings/errors are shown.

Can you go back and do a bit more debugging for me/us? I understand what
you are saying, except for one problem: MajorCool does not "write out" the
config file -- that is handled by Majordomo. It still could be possible
that MajorCool is handing a truncated version of the text to Majordomo, but
it could be just as likely that you have found a problem with Majordomo
itself rather than MajorCool...


--bill




Follow-Ups:
References:
Indexed By Date Previous: Re: Create and Delete with MAJORCOOL
From: Bill Houle <Bill.Houle@SanDiegoCA.NCR.COM>
Next: Re: on behalf of?!?!
From: "Brian L. Heess" <dmbong@commline.com>
Indexed By Thread Previous: MajorCool (1.3.0) truncating restrict_post on modify
From: Richard Hopkins <Richard.Hopkins@bristol.ac.uk>
Next: Re: MajorCool (1.3.0) truncating restrict_post on modify
From: Richard Hopkins <Richard.Hopkins@bristol.ac.uk>

Google
 
Search Internet Search www.greatcircle.com