Great Circle Associates Majordomo-Users
(July 1994)
 

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

Subject: Re: Clarifications
From: Brent Chapman <brent @ mycroft . GreatCircle . COM>
Date: Fri, 29 Jul 1994 14:15:44 -0700
To: "Anant Bukkapatnam - FES" <abukkapa @ pcocd2 . intel . com>
Cc: majordomo-users @ greatcircle . com
In-reply-to: Your message of Fri, 29 Jul 1994 08:28:42 -0700

"Anant Bukkapatnam - FES" <abukkapa@pcocd2.intel.com> writes:

# Hi  all,
# 	I am running majordomo1.62 on our site.  Last week
# I had problems which were beyond me at that point to solve.
# I posted for some help but seems like none of you have seen that
# problem.   Here is the problem,
# 
# 	1.  I get the following error when somebody tried to
# subscribe to the list,
# 
# 	MAJORDOMO ABORT
# 	Can't append to /usr/local/majordomo/LISTS/shrlist: Interrupted system
# call
# 
# Any ideas on this.  Infact this is working  NOW again fine without any
# changes what so ever to majordomo.   This leads me to think,
# that there could have been some of the following problems,
# 
# 	a.  Since this list was new and opened to everybody,  suddenly
# there were lots of users trying to subscribe.  After allowing some of the  them
# to
# subscribe, majordomo failed on some concurrent processing ( I think the locking
# failed for some reason,  IF I am right).   There were atleast 50 users rejected
# with
# this problem and I got 50+ mails from majordomo complaining the problem.

This is what happens when Majordomo eventually gives up after 10
minutes of trying once per second to get a lock on a file
(/usr/local/majordomo/LISTS/shrlist in the example given above).  This
could be because Majordomo doesn't have write permissions for the
directory the file is in, or it could be because the file really was
locked for 10 minutes by other Majordomo processes.

# ****************************************************************
# 	2.  This is a question which is totally unrelated to the above one,
# Is it possible in majordomo 1.62 to reject mail from other domains.  This  will
# help because the lists can be maintained with security and some of the users
# will not have concerns  about it.  I keep hearing about "munge  domain" ,  I
# believe
# this is the feature in majordomo1.93.  I am not clear on what it is.  Can
# somebody
# explain me about this.

munge_domain is a feature of 1.9x that tells Majordomo to treat
addresses "user@bar.com" and "user@foo.bar.com" as identical (without
munge_domain, and in all versions prior to 1.9x, Majordomo views those
as different addresses).


-Brent
--
Brent Chapman         | Great Circle Associates  | Call or email for info about
Brent@GreatCircle.COM | 1057 West Dana Street    | upcoming Internet Security 
+1 415 962 0841       | Mountain View, CA  94041 | Firewalls Tutorial dates


Indexed By Date Previous: get & index, and who/what should I alias majordom to?
From: dmp@epg.harris.com (Donald Patterson)
Next: Dec Alpha and Core Dumps
From: "Steven L. Tamm" <tamm@kilpikonna.media.mit.edu>
Indexed By Thread Previous: Clarifications
From: "Anant Bukkapatnam - FES" <abukkapa@pcocd2.intel.com>
Next: get & index, and who/what should I alias majordom to?
From: dmp@epg.harris.com (Donald Patterson)

Google
 
Search Internet Search www.greatcircle.com