Date: Wed, 17 Apr 1996 16:22:34 -0600 (MDT) From: Dave Andersen <angio@aros.net> To: hjohnson@gw.tacsys.com (Howard Johnson) Cc: questions@FreeBSD.org Subject: Re: Configuration problems? Message-ID: <199604172222.QAA11101@shell.aros.net> In-Reply-To: <Pine.BSF.3.91.960417134158.8163A-200000@gw.tacsys.com> from Howard Johnson at "Apr 17, 96 01:46:26 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
The problem is most likely that it can't write to the logfile. Make sure
the permissions on this file and all of the directories are set correctly
-- 9 times out of 10, when Majordomo has a problem, it's a permissions
problem.
Also check to make sure that the wrapper program is working properly.
-Dave Andersen
Lo and behold, Howard Johnson once said:
> I have installed majordomo v1.93 on my FreeBSD machines without success.
>
> Executing the documented test procedure "echo help | /usr/sbin/sendmail
> -v majordomo" causes a memory fault. The hard drive just keeps thrashing
> and eventually the memory fault message appears. It's as though the
> program is stuck in a loop and chewing up memory as it goes along.
>
> I have tried the setup on a machine that has 64MB so I know I am not out
> of memory.
>
> Attached is my /etc/majordomo.cf file.... any help would be greatly
> appreciated.
>
> Howard Johnson
> TAC Systems
Content-Description:
> # $whereami -- What machine am I running on?
> $whereami = "tacsys.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/bin";
> }
>
> # $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 = "/var/log/majordomo";
>
> # $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 = "/usr/local/majordomo/archive";
> $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 = ( "/spool/archive/bblisa", "/usr/spool/archive/firewalls" );
>
>
> # 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;
> # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $
>
--
angio@aros.net Complete virtual hosting and business-oriented
system administration Internet services. (WWW, FTP, email)
http://www.aros.net/ http://www.aros.net/about/virtual
"There are only two industries that refer to thier customers as 'users'."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604172222.QAA11101>