Great Circle Associates Majordomo-Users
(October 1993)
 

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

Subject: Re: Coping with "MAJORDOMO ABORT" ?
From: Brent Chapman <brent @ mycroft . GreatCircle . COM>
Date: Tue, 19 Oct 1993 13:23:45 -0700
To: andy @ homebase . vistachrome . com (Andy Finkenstadt)
Cc: majordomo-users @ greatcircle . com
In-reply-to: Your message of Tue, 19 Oct 1993 16:00:47 -0400 (EDT)

andy@homebase.vistachrome.com (Andy Finkenstadt) writes:

# Well, I managed to stress out majordomo. :-)  
# 
# I am taking over the rec.arts.erotica mailing list reflector, and have
# had subscription requests out the wazoo.  Apparently when someone asks
# to be subscribed to the list and someone else asks for a list of lists,
# they collide and the lists command aborts out.  Please note the times
# in the capture below:
# 
# Oct 19 12:31:18 cyan majordomo[2761] {person1} subscribe erotica person1
# Oct 19 12:31:23 cyan majordomo[2821] {person2} lists
# Oct 19 12:31:28 cyan majordomo[2808] {person3} subscribe erotica person3
# Oct 19 12:31:29 cyan majordomo[2821] {person2}  (split to next line)
#   ABORT Can't open list /usr/local/lib/majordomo/lists/shlock2781 
# Oct 19 12:31:31 cyan majordomo[2808] {person3} help
# 
# Notice that person3's job is still being processed apparently with
# a "subscribe" "help" set of lines.
# 
# I can think of three things that can help this situation:  
#   1. change shlock.pl to use the parent directory or /tmp for its lock file
#   2. change lists to lock the directory while it does its stuff
#   3. change lists to skip any files beginning 'shlock'
#  
# Could this be a real bug, or do I have my system configured incorrectly,
# or should I already have done 1 or 2 by virtue of applying previously 
# mentioned patches?  (I am using the release of majordomo available a
# week ago.)

No, it's a real bug, which I first stumbled across last month.
Basicly, the problem is that, as far as Majordomo is concerned,
"shlock12345" (which is the form of temporary files that "shlock"
creates) is a valid name for a mailing list.  The solution is to use
"shlock.12345" instead; since this has a "." in it, Majordomo doesn't
think it's a valid list name.  A patch to do this is included below;
this is in the next release.


-Brent
--
Brent Chapman                                   Great Circle Associates
Brent@GreatCircle.COM                           1057 West Dana Street
+1 415 962 0841                                 Mountain View, CA  94041


6,7c6,7
< # $Revision: 1.6 $
< # $Date: 1993/04/16 23:21:31 $
---
> # $Revision: 1.7 $
> # $Date: 1993/10/19 20:21:34 $
114c114
< 	$tempname .= "shlock$$";
---
> 	$tempname .= "shlock.$$";
116c116
< 	$tempname = "shlock$$";
---
> 	$tempname = "shlock.$$";


Indexed By Date Previous: Coping with "MAJORDOMO ABORT" ?
From: andy@homebase.vistachrome.com (Andy Finkenstadt)
Next: Creation of mailing lists via email?
From: kovar@NDA.COM (David Kovar)
Indexed By Thread Previous: Coping with "MAJORDOMO ABORT" ?
From: andy@homebase.vistachrome.com (Andy Finkenstadt)
Next: Creation of mailing lists via email?
From: kovar@NDA.COM (David Kovar)

Google
 
Search Internet Search www.greatcircle.com