At 4:40 PM 1/10/96, Mark Cheverton wrote:
>Hi,
> I have just moved majordomo from one machine to another
>making the mistake of not setting the group permission on
>/usr/local/etc/majordomo to write. THis had the following
>interesting effect:
> Someone would subscribe and they would get back a succeded
>message, but majordomo hadnt actually done it but was in the process.
>Hence it had locked the list file and was trying to update it. The
>mailer quit with unknown error 13 and every hour (how the sendmail
>is configured) tried to send the subscription message again causeing
>another subscription succeeded message to be sent out but still not
>being able to do anything on the locked file.
> I know this is because I had it setup wrongly but maybe majordomo
>should be written so that it only sends out the succeeded message when
>its actually done and put you on the list - avoiding such repeated email
>loops.
It _was_ written that way originally. Success messages didn't go out until
the action had actually succeeded. If that's no longer true, then somebody
made the change in later versions when I wasn't looking, and I think it was
a bad idea.
-Brent
----------------------+----------------------------+------------------------
Brent Chapman | Great Circle Associates | 1057 West Dana Street
Brent@GreatCircle.COM | http://www.greatcircle.com | Mountain View, CA 94041
----------------------+----------------------------+------------------------
Internet Tutorials from the Experts!
|
|
