"Brent Chapman" <Brent@GreatCircle.COM> writes:
"Stephen Bannasch" <stephen_bannasch@terc.edu> writes:
> # Subject: multiple unsubscribes
> # I am the owner of a list and wanted to remove a bunch a bad addresses
> # so I tried the following commands:
> #
> # approve PASSWORD unsubscribe MYLIST USER1
> # approve PASSWORD unsubscribe MYLIST USER2
> # approve PASSWORD unsubscribe MYLIST USER3
> #
> # Majordomo responded by only unsubcribing the first person on the
> # list.
> # The second and third were reported as not being members of MYLIST.
> # When
> # the unsubscribe requests for users 2 and 3 were placed in their own
> # messages the unsubscribe operations were successful.
> #
> # Is this a bug? Is there a fix?
>
> It should work. I suspect some sort of locking/caching problem. Are
> your list files on the local disk of the machine Majordomo is running
> on, or are they accessed via NFS?
I'm having the same problem. The list files are definitely on the
disk of the machine upon which Majordomo is running.
I put some log statements in majordomo.pl, specifically in the
is_list_member function. The function operates properly for the first
call to it (from do_unsubscribe), but subsequent calls never enter the
while loop after opening the list file. (Note that the open doesn't
give an error.)
Any ideas?
Kingsley F. Kerce (kerce@scri.fsu.edu)
Supercomputer Computations Research Institute
Florida State University
Tallahassee, FL, USA 32306
Follow-Ups:
|
|
