Great Circle Associates Majordomo-Users
(May 1995)
 

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

Subject: help! segmentation violation
From: Agris Taurins <taurins @ penguin . inetnebr . com>
Date: Wed, 24 May 1995 02:04:57 -0500 (CDT)
To: majordomo-users @ greatcircle . com

I could use some help, I've beaten my head against a wall long enough.  It's
starting to feel good.

I'm trying to install majordomo on a Linux (1.2.5) box.  I'm running Perl5.001.
I have majordomo version 1.93.  I've read the README file, the FAQ and the
O'Reilly file.  I believe my permissions are correct; I have a user and group
called "majordom" and all the files under /usr/local/majordomo are in-fact owned
by majordomo.  They all have at least 660 and in most cases 664 permissions on
said files.  I've gone through and changed request-answer with the
"require shlock.pl" and changing the exec_sendmail stuff around.  I've gone
through the perl scripts looking for inappropriate "@" lurking around and
changed them to "\@".  The following two tests DO work correctly:

	echo help | /usr/lib/sendmail -v majordomo
	echo help | /usr/lib/sendmail -v sample-request

They also work correctly if sent from another machine to mine:

	echo help | /usr/lib/sendmail -v majordomo@penguin.inetnebr.com
	echo help | /usr/lib/sendmail -v sample-request@penguin.inetnebr.com

BUT when I try the following test:

	echo "subscribe sample" | /usr/lib/sendmail -v majordomo

I get the following output:

	majordomo... aliased to "| /usr/local/majordomo/bin/wrapper majordomo"
	"| /usr/local/majordomo/bin/wrapper majordomo"... Connecting to penguin.inetnebr.com (prog)...
	sh died because of segmentation violation (11)--requeueing message
	"| /usr/local/majordomo/bin/wrapper majordomo"... Deferred

(The same result happens when I try and do anything other than the tests I've
already mentioned)

WHAT have I done wrong?  After searching this long it's either a brand-spanking-
new problem that's deeply rooted and will take man-years to fix :-) or I've
overlooked something dreadfully obvious.  Please point out my stupid mistake(s).

My majordomo.cf and /etc/aliases files follow:

----------------------------------------------------------------------------
majordomo.cf
----------------------------------------------------------------------------
# $whereami -- What machine am I running on?
$whereami = "penguin.inetnebr.com";

# $whoami -- Who do users send requests to me as?
$whoami = "Majordomo@$whereami";

# $whoami_owner -- Who is the owner of the above, in case of problems?
$whoami_owner = "Owner-Majordomo@$whereami";

# $homedir -- Where can I find my extra .pl files, like majordomo.pl?
# the environment variable HOME is set by the wrapper
if ( defined $ENV{"HOME"}) {
     $homedir = $ENV{"HOME"};
} else {
     $homedir = "/usr/local/majordomo";
}

# $listdir -- Where are the mailing lists?
$listdir = "/usr/local/majordomo/lists";

# $digest_work_dir -- the parent directory for digest's queue area
# Each list must have a subdirectory under this directory in order for
# digest to work. E.G. The bblisa list would use:
#       /usr/local/mail/digest/bblisa
# as its directory.
$digest_work_dir = '/usr/local/majordomo/digest';

# $log -- Where do I write my log?
$log = "$homedir/Log";

# $mailer -- What program and args do I use to send mail?
# The variable $to can be interpolated into this command line,
# however the $to variable is provided by the person sending mail,
# and much mischief can be had by playing with this variable.
# Use $to with care.
$mailer = "/usr/lib/sendmail -f\$sender -t";

# Majordomo will look for "get" and "index" files related to $list in
# directory "$filedir/$list$filedir_suffix", so set $filedir and
# $filedir_suffix appropriately.  For instance, to look in
# /usr/local/mail/files/$list, use:
#   $filedir = "/usr/local/mail/files";
#   $filedir_suffix = "";               # empty string
# or to look in $listdir/$list.archive, use:
#   $filedir = "$listdir";
#   $filedir_suffix = ".archive";

$filedir = "$listdir";
$filedir_suffix = ".archive";

# What command should I use to process an "index" request?
$index_command = "/bin/ls -lRL";

# If you want to use FTPMAIL, rather than local access, for file transfer
# and access, define the following:
#   $ftpmail_address = "ftpmail@decwrl.dec.com";
#   $ftpmail_location = "FTP.$whereami";

# if you want the subject of the request to be included as part of the
# subject of the reply (useful when automatically testing, or submitting
# multiple command sets), set $return_subject to 1.
$return_subject = 1;

# If you are using majordomo at the -request address, set the
# following variable to 1. This affects the welcome message that is
# sent to a new subscriber as well as the help text that is generated.
$majordomo_request = 0;

# Set the umask for the process. Used to set default file status for
# config file.
umask(007);

# the safe locations for archive directories. This should be defined as
# a series of root anchored directory paths as will be used as prefixes
# to the file names specified to the archive2.pl script.
@archive_dirs = ( "/u/majordomo" );


# Set this to 1 if you want to use the experimental mechanism for allowing
# / in user names. People with lots of X.400 addresses on their lists or
# HP mail whatever may want to set this. However use it at your own risk.
$analyze_slash_in_address = 0;

#
# these tune the experimental matching that is done for addresses with / in
# them. If you haven't turned on the experimental analyze_slash_in_address
# they are ignored. See the source for full explanation of these variables.
#
# if set to 1 ignore the requirement that addresses have an @ sign in the
# address component after the last /.
$no_x400at=0;
# if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address.
# X.400 seems to require these components.
$no_true_x400=0;

1;
----------------------------------------------------------------------------
/etc/aliases
----------------------------------------------------------------------------
# Aliases for majordomo
owner-owner:            postmaster
majordomo:              "| /usr/local/majordomo/bin/wrapper majordomo"
majordom:               owner-majordomo
majordomo-owner:        taurins
owner-majordomo:        majordomo-owner

#
# Sample mailing list
#
owner-sample:           sample-owner
sample:         "| /usr/local/majordomo/bin/wrapper resend -p bulk -M 10000 -R -l sample -f Sample-Owner -h penguin.inetnebr.com -s sample-outgoing"
sample-owner:           taurins
sample-approval:        sample-owner
sample-outgoing:        :include:/usr/local/majordomo/lists/sample, sample-archive
owner-sample-outgoing:  sample-owner
#sample-archive:        /usr/local/majordomo/archive/sample/sample
sample-archive:         /u/majordomo/sample
owner-sample-archive:   sample-owner
sample-request:         "| /usr/local/majordomo/bin/wrapper request-answer sample"
owner-sample-request:   sample-owner
--------------------------------------------------------------------------------

-- 
Agris Taurins	(taurins@penguin.inetnebr.com)	..this sig under construction..



Follow-Ups:
Indexed By Date Previous: Re: Majordomo and large listser
From: hal9001@panix.com (Robert A. Rosenberg)
Next: CGI Interface from WWW to Majordomo
From: mcollins@lnd.state.az.us (Micheal Collins Intern)
Indexed By Thread Previous: Re: Majordomo and large listser
From: "Michel Daulie" <ccs.daulie.m@alpha.ufsia.ac.be>
Next: Re: help! segmentation violation
From: Operator <root@kvsmail.rz.go.dlr.de>

Google
 
Search Internet Search www.greatcircle.com