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/
drwxrwxr-x 2 majordom majordom 1024 Sep 4 17:14 Tools/
drwxrwxr-x 2 majordom majordom 1024 Sep 4 17:15 bin/
-rwxr-xr-x 1 majordom majordom 2615 Sep 10 17:30 bounce-remind*
-rwxr-xr-x 1 majordom majordom 43737 Sep 10 17:30 config_parse.pl*
-rwxr-xr-x 1 majordom majordom 11320 Sep 10 17:30 digest*
drwx------ 2 majordom majordom 1024 Sep 10 16:18 mail/
-rwxr-xr-x 1 majordom majordom 42524 Sep 10 17:30 majordomo*
-rw-r--r-- 1 majordom majordom 3708 Sep 10 17:33 majordomo.cf
-rw-r--r-- 1 majordom majordom 3697 Sep 4 17:12 majordomo.cf.example
-rw-r--r-- 1 majordom majordom 3708 Sep 10 17:33 majordomo.cf.perm
-rwxr-xr-x 1 majordom majordom 14327 Sep 10 17:30 majordomo.pl*
-rw-r--r-- 1 majordom majordom 141 Sep 10 17:30 majordomo_version.pl
drwxrwxr-x 4 majordom majordom 1024 Sep 4 17:12 man/
-rwxr-xr-x 1 majordom majordom 2153 Sep 10 17:30 new-list*
-rwxr-xr-x 1 majordom majordom 3024 Sep 10 17:30 request-answer*
-rwxr-xr-x 1 majordom majordom 12872 Sep 10 17:30 resend*
-rw-r--r-- 1 majordom majordom 3742 Sep 10 17:30 resend.README
-rwxr-xr-x 1 majordom majordom 6183 Sep 10 17:30 shlock.pl*
-rwxr-xr-x 1 majordom majordom 131 Sep 10 17:30 test*
-rwxr-xr-x 1 root majordom 6432 Sep 10 17:00 wrapper*
> 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':
icarus:/usr/local/majordomo-1.93$ ./test
euid is: 503
egid is: 100 100
ruid is: 503
rgid is: 100 100
icarus:/usr/local/majordomo-1.93$ ./wrapper test
euid is: 503
egid is: 100 100
ruid is: 503
rgid is: 100 100
BTW, this is on a linux box, kernel 1.2.13.
> 3) Do your aliases use wrapper to invoke the Mj programs?
Yes, here are the aliases:
# MajorDomo Aliases
majordomo: "|/usr/local/majordomo-1.93/wrapper majordomo"
owner-majordomo: buffalo
majordomo-owner: buffalo
# The 'mylist' test list:
mylist: :include:/usr/local/mail/lists/mylist
owner-mylist: buffalo
mylist-request: "|/usr/local/majordomo-1.93/wrapper request-answer mylist"
mylist-approval: buffalo
> 4) If you're running Perl 5, is your version of Perl at least 5.001e
> (perl -v will display the perl version). Perl 4.019 through 4.036
> will work, but 5.000 through 5.001d will not. Version 5.003 is
> recommended (as of this writing) if you need to upgrade. Note that
> some changes are required in the Mj Perl files for Perl 5 (all '@'
> characters in quotish strings must be escaped, e.g. "user@host.net"
> must be changed to "user\@host.net").
I'm running the latest version of Perl, and I've gone through all the MJ
Perl files to escape the '@' in email addresses...
Any more ideas anyone?
--Duncan
Follow-Ups:
References:
|
|
