As for the bin part, I had the same thing. Change the UID for majordom
to below 99. I use 54 and this seemed to fix my problem. All you need
to do is change the uid in the /etc/passwd file , change the UID in the
Makefile and do a make install-wrapper. Then cp the wrapper to the
apropriate directory. This has fixed (I believe) my wrapper "bin"
problem.
I has also use the UID of 504 (well close to yours). I could get it to
work but I had to use cron files and shell scripts to change the
permissions to majordom.majordom. I don't think this is in the FAQ or
manual. I saw someone mention it in another post so I reinstalled my
wrapper because of that post.
Keith
On Wed, 1 May 1996, World of Coasters wrote:
> This is posted in 2 parts, as it seems there is a file limit
> on this list.
>
> ***PART 1.***
>
> OK. I removed everythign and started again. Below you will find
> ALL of my files, directory listings and such. Now, When I do a
> 'help', majordomo goes into it's loop, then I kill it, and after
> that I get the help file mailed to me. For some reason though,
> majordomo spawns back up and does this every 5-10 minutes. I have
> to keep killing the process and then it mailes me the help file.
> No matter what I do, I cannot get it to run under majordom. My
> UID for majordom is 502 and gid is 16, but under top it shows
> up as bin! Any help would be appreciated.
>
> BTW, I included the makefile at the bottom. I get 2 warnings
> when compiling. Here they are:
>
> tmb:/tmp/majordomo-1.93# make
> cc -DBIN=\"/usr/local/majordomo-1.93\" -DPATH=\"PATH=/bin:/usr/bin:/usr/local/mc
> wrapper.c: In function `main':
> wrapper.c:65: warning: comparison between pointer and integer
> wrapper.c:99: warning: initialization makes integer from pointer without a cast
>
> Lastly, as I wrote this, majordomo started up again!!! I read in
> the readme that if it has a problem locking it will try every
> minute for 10 minutes, but this is every 3-5 minutes and it's
> agrivating!
>
> One more thing. This is what I get when I try to subscibe to my
> woc_list list. I usually see a success on majordomo msgs, but
> mine does not send any confirmation:
>
> --
>
> >>>> subscribe woc_list
>
>
> ------------------------------------------------------------------------
> DIRECTORY LISTINGS:
> ------------------------------------------------------------------------
>
> drwxr-xr-x 12 root root 1024 Apr 30 18:53 ./
> drwxr-xr-x 22 root root 1024 Nov 12 17:52 ../
> drwxr-xr-x 2 root bin 1024 Apr 30 19:03 bin/
> drwxr-xr-x 3 root root 1024 Nov 12 18:12 doc/
> drwxr-xr-x 2 root root 1024 Mar 16 1994 include/
> drwxr-xr-x 2 root root 1024 Nov 24 1993 info/
> drwxr-xr-x 3 root root 1024 Jan 8 17:11 lib/
> drwxr-xr-x 5 root root 1024 Apr 28 22:39 mail/
> drwxrwxr-x 5 majordom majordom 1024 Apr 30 19:32 majordomo-1.93/
> drwxr-xr-x 22 root root 1024 Nov 12 17:17 man/
> drwxr-xr-x 8 root root 1024 Apr 26 22:08 sbin/
> drwxr-xr-x 2 root root 1024 Nov 24 1993 src/
>
> tmb:/usr/local/majordomo-1.93# ls -al
> total 167
> drwxrwxr-x 5 majordom majordom 1024 Apr 30 19:32 ./
> drwxr-xr-x 12 root root 1024 Apr 30 18:53 ../
> -rw-rw-r-- 1 majordom majordom 1 Apr 30 19:32 Log
> drw-rw-r-- 2 majordom majordom 1024 Apr 30 19:01 Tools/
> drw-rw-r-- 2 majordom majordom 1024 Apr 30 19:01 bin/
> -rwxr-xr-x 1 majordom majordom 2615 Apr 30 19:26 bounce-remind*
> -rw-r--r-- 1 majordom majordom 43737 Apr 30 19:26 config_parse.pl
> -rwxr-xr-x 1 majordom majordom 11320 Apr 30 19:27 digest*
> -rwxr-xr-x 1 majordom majordom 42524 Apr 30 19:26 majordomo*
> -rw-r--r-- 1 majordom majordom 3695 Apr 30 19:28 majordomo.cf
> -rw-r--r-- 1 majordom majordom 14327 Apr 30 19:27 majordomo.pl
> -rw-r--r-- 1 majordom majordom 141 Apr 30 19:27 majordomo_version.pl
> drw-rw-r-- 4 majordom majordom 1024 Apr 30 19:01 man/
> -rwxr-xr-x 1 majordom majordom 2153 Apr 30 19:27 new-list*
> -rwxr-xr-x 1 majordom majordom 3024 Apr 30 19:27 request-answer*
> -rwxr-xr-x 1 majordom majordom 12872 Apr 30 19:27 resend*
> -rw-r--r-- 1 majordom majordom 3742 Apr 30 19:27 resend.README
> -rw-r--r-- 1 majordom majordom 6183 Apr 30 19:27 shlock.pl
> -rwxr-xr-x 1 majordom majordom 131 Apr 30 19:27 test*
> -rwxr-xr-x 1 root majordom 6324 Apr 30 19:27 wrapper*
>
> drwxr-xr-x 5 root root 1024 Apr 28 22:39 ./
> drwxr-xr-x 12 root root 1024 Apr 30 18:53 ../
> drwxrwxr-x 2 majordom majordom 1024 Apr 28 22:39 archive/
> drwxrwxr-x 2 majordom majordom 1024 Apr 28 22:39 digest/
> drwxrwxr-x 2 majordom majordom 1024 Apr 30 19:35 lists/
>
> All files under lists are 664. I have yet to set up a digest and
> archive. But I did make the proper lists. I think:
> drwxrwxr-x 2 majordom majordom 1024 Apr 30 19:35 ./
> drwxr-xr-x 5 root root 1024 Apr 28 22:39 ../
> -rw-rw-r-- 1 majordom majordom 1 Apr 30 19:34 woc_list
> -rw-rw-r-- 1 majordom majordom 47 Apr 30 19:35 woc_list.info
> -rw-rw-r-- 1 majordom majordom 1 Apr 30 19:35 woc_list.passwd
>
> --------------------------------------------------------------------------
> CONFIG FILE:
> --------------------------------------------------------------------------
>
> # $whereami -- What machine am I running on?
> $whereami = "rollercoaster.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 = "Majordomo-Owner@$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-1.93";
> }
>
> # $listdir -- Where are the mailing lists?
> $listdir = "/usr/local/mail/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/mail/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 = ( "/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.
> #
>
> ***END PART 1***
> --
> Jim Serio jim@rollercoster.com
> Maintainer: World of Coasters - http://www.rollercoaster.com
> The Web's Premier Coaster Site!
>
---------------------------
Keith Reding, Ph.D.
Biotechnologist
kreding@info.aphis.usda.gov
APHIS Mailing List Manager
(301) 734-8365
http://www.aphis.usda.gov/
--------------------------
References:
-
Arghhhhh!!!
From: World of Coasters <jim@rollercoaster.com>
|
|
