Great Circle Associates Majordomo-Users
(September 1996)
 

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

Subject: Re: Runaway Majordomo Process
From: Dave Wolfe <dwolfe @ risc . sps . mot . com>
Date: Tue, 10 Sep 1996 17:11:55 -0500 (CDT)
To: buffalo @ icarus . yml . com (Duncan D. Sterling)
Cc: majordomo-users @ greatcircle . com
In-reply-to: <Pine.LNX.3.91.960910171046.1180L-100000@icarus.yml.com> from "Duncan D. Sterling" at Sep 10, 96 05:47:43 pm
Reply-to: Dave Wolfe <david_wolfe @ risc . sps . mot . com>

[ Duncan D. Sterling writes: ]
> 
> On Mon, 9 Sep 1996, Dave Wolfe wrote:
> 
> Majordomo still runs away when invoked....
> 
> > 1)  Do the ownerships and permissions on the list files, log file, and
> >     the directories where they reside allow the majordomo user to write
> >     to the files and create files in the directories?
> 
> Yes, all are majordom/majordom, 664 files, 755 dirs (except the 
> executables, naturally):
> 
> drwxrwxr-x   2 majordom majordom     1024 Sep 10 11:12 Log/

Depending on what you have specified in your majordomo.cf, this should
be a *file*, not a directory. And the directory the log file resides
must be writable by Mj so it can create lock files to log messages.

> > 2)  Is wrapper configured and installed correctly? It must be owned by
> >     root and setuid (BSD-based systems are different: see Makefile).
> >     You can test this by logging on as a user other than root or your
> >     majordomo user and running the following *exactly as shown*:
> > 
> > 	./test
> > 	./wrapper test
> > 
> >     The first should show the uid/gids of the logon user. The second
> >     should show the majordomo uid/gids. If not, you don't have wrapper
> >     installed and/or configured correctly. Note that wrapper must be
> >     installed by the superuser (root) in order to set the owner and
> >     setuid permissions.
> 
> Strange, no matter how I recompile the wrapper (as root, using POSIX or BSD
> settings in the Makefile), I get the same result from ./test and ./wrapper
> test, when I run them as a non root, non majordom user, ie, logged in as 
> user 'testuser':

That's because wrapper is *not* installed properly. You must be root
when you run 'make install'.

> -rwxr-xr-x   1 root     majordom     6432 Sep 10 17:00 wrapper*
     ^
This should be 's' to indicate setuid so that wrapper can do its job,
i.e. change the uid/gid to the majordom user/group. You can fix this by
becoming root and doing:

    chmod 4755 wrapper

> mylist: :include:/usr/local/mail/lists/mylist

Note that this alias doesn't invoke resend, so you won't get any of
resend's features.

-- 
 Dave Wolfe    *Not a spokesman for Motorola*
 Motorola MMTG  6501 Wm. Cannon Dr. W. OE112  Austin  TX  78735-8598


Follow-Ups:
References:
Indexed By Date Previous: Re: Runaway Majordomo Process
From: "Duncan D. Sterling" <buffalo@icarus.yml.com>
Next: Installing majordomo 1.93
From: Rasana Atreya <Rasana.Atreya@library.ucsf.edu>
Indexed By Thread Previous: Re: Runaway Majordomo Process
From: "Duncan D. Sterling" <buffalo@icarus.yml.com>
Next: Re: Runaway Majordomo Process
From: "Duncan D. Sterling" <buffalo@icarus.yml.com>

Google
 
Search Internet Search www.greatcircle.com