-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 12 Mar 1997, Dave Wolfe wrote:
>[ Phillip Jones writes: ]
>>
>> When I send a "Help", majordomo complians a bout not being able to
>> open a log file, And when I send a command like "lists" It aborts
>> because it can't get a lock file. No indications of trouble came up
>> in ./wrapper config-test, and nothing looked wrong until I tested it.
>> I have tried severail file permisions including 0666 on all concerned
>> file, but with no luck. I'm running (Slackware 96), Kernel v.2.0.28.
>
>Mj has to be able to create lock files in the directories of all the
>files it accesses, so you need to be sure it has write permissions for
>those directories as well as the files. Also be sure you ran config-test
>as an ordinary user, not as root or your majordom user.
>
>--
> Dave Wolfe
>
Unfortanatly, I've checked for that, and all is as you said ( I've included
exactly what I did in a attachment. )
I get the same error if I catualy go throught the mail system, and not just
simulate a message w/ the "( echo ) | " stufs.
"Olivia C. Williamson" <olivia@stanford.edu> Wrote that he had a simular
problem that was fixed by using "bin"'s GID, but that didn't fix it either.
-Phillip Jones
[-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-]
Unix is the worst operating system; except for all others.
-- Berry Kercheval
Finger me for pgp key.
pub 2047/BD80E335 1996/11/21 Mouse
pub 2047/AE3D4C3D 1996/07/03 mouse
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQEVAwUBMybxpcaYQsi9gOM1AQGROAf/XFmW9jb0oUbp8H75Wd5Jb1LMUiBnkvD0
BqGIw3eVsWnMOjI8onnKWJKPA8adMlAAjpgfoIkm7UN0gzOmNWmGG2GVRO9c7HeG
D/4DyM3KqkuZi951PbS+npQ1CbxaieX2IKfKzC/76+A9nxOfBf/lX8G1fa/6KNik
MmFHiLvnLKuTQYiox6FrqR4wHqvYe6jkJE17Qe8D3Z8+fQP+QKkbetDqR5NYcNrr
gkK10/BE5lxF41xRbmHGKSvHFxv+00BxGXAtjEJkrayzaQ+Tm0PR2StWORT2BHUD
EtZqMrD5otChgEaoICD9qKSVHJc6YCcFP7Uxva1SwQXdA39SCAMkbA==
=wF0o
-----END PGP SIGNATURE-----
anx0824:/usr/home/mouse$ id
uid=503(mouse) gid=100(users) groups=100(users)
anx0824:/usr/home/mouse$ cd ~exploits
anx0824:/home/exploits$ cd mjd
anx0824:/home/exploits/mjd$ ./wrapper config-test
Config-test for Majordomo
Obvious things:
environment variables
HOME=/usr/home/exploits/mjd
LOGNAME=mouse
MAJORDOMO_CF=/usr/home/exploits/mjd/majordomo.cf
PATH=/bin:/usr/bin:/usr/ucb
SHELL=/bin/sh
TZ=EST
USER=mouse
euid/egid checks
effective user = exploits (uid 401)
effective group = daemon users (gid 2 100 )
uid/gid checks
real user = exploits (uid 401)
real group = daemon users (gid 2 100 )
Non obvious things that cause headaches:
Good: 'require'd /usr/home/exploits/mjd/majordomo.cf okay.
Good: found ctime.pl okay.
Good: found majordomo_version.pl okay.
Good: found majordomo.pl okay.
Good: found shlock.pl okay.
Good: found config_parse.pl okay.
You're running Majordomo Version 1.94.1.
--==> Majordomo home directory is /home/exploits/mjd.
Include directories
/home/exploits/mjd
/usr/lib/perl5/i586-linux/5.003
/usr/lib/perl5
/usr/lib/perl5/site_perl/i586-linux
/usr/lib/perl5/site_perl
.
Home
Good: changedir to /home/exploits/mjd succeeded.
Good: Created a mock lock file.
temp directory
Good: Created a temp file in $TMPDIR (/usr/tmp).
list directory
Good: list directory /home/exploits/mjd/lists has good permissions.
log
Good: logfile /home/exploits/mjd/Log exists and is writeable.
Mailers
You have defined a mailer for delivery.
Attempting to verify that this is a valid mailer...looks okay.
You have defined a mailer for delivering administrative messages.
Attempting to verify that this is a valid mailer...looks okay.
Checking majordomo.cf
Checking to see if there are new variables that should be in
your majordomo.cf file...
Have you configured where Majordomo is?
$whereami is anx0824.slip.appstate.edu
Good: yup!
end of tests
Nothing bad found! Majordomo _should_ work correctly.
If it doesn't, check your configuration file
(/usr/home/exploits/mjd/majordomo.cf)
closely, and if it still looks okay, consider asking the majordomo-users
mailing list at "majordomo-users@greatcircle.com" for assistance. Be sure
and fully specify what your problems are, and what type of machine (and
operating system) you are using.
Enjoy!
anx0824:/home/exploits/mjd$ grep exploits /etc/sendmail.cf
OA/home/exploits/mjd/majordomo.aliases
Texploits
anx0824:/home/exploits/mjd$ (echo From: mouse;echo To:
majordomo@anx0824.slip.appstate.edu;echo ;echo help;echo ) | ./wrapper
majordomo
majordomo[895] {mouse} help
anx0824:/home/exploits/mjd$
New mail for mouse@anx0824 has arrived:
----
From: Majordomo@anx0824.slip.appstate.edu
Subject: Majordomo results
--
>>>> help
This is the "Majordomo" mailing list manager, version 1.94.1.
...more...
You have mail in /var/spool/mail/mouse
anx0824:/home/exploits/mjd$ ls -laid Log
12201 -rw-rw-r-- 1 exploits daemon 0 Mar 12 12:21 Log
anx0824:/home/exploits/mjd$ id exploits
uid=401(exploits) gid=2(daemon)
anx0824:/home/exploits/mjd$ su -
Password:
Linux 2.0.0.
You have mail.
E Pluribus Unix
anx0824:/var/spool/mail# cat root
From Majordomo-Owner@anx0824.slip.appstate.edu Wed Mar 12 17:24:38 1997
Return-Path: <Majordomo-Owner@anx0824.slip.appstate.edu>
Received: (from exploits@localhost) by anx0824.slip.appstate.edu
(8.8.3/8.8.3) id RAA00897; Wed, 12 Mar 1997 17:24:38 GMT
Date: Wed, 12 Mar 1997 17:24:38 GMT
Message-Id: <199703121724.RAA00897@anx0824.slip.appstate.edu>
To: Majordomo-Owner@anx0824.slip.appstate.edu
From: Majordomo@anx0824.slip.appstate.edu
Subject: MAJORDOMO NOTICE: Can't open log
Reply-To: Majordomo@anx0824.slip.appstate.edu
Status: O
X-Status:
--
majordomo[895] {mouse} help
anx0824:/var/spool/mail# exit
logout
anx0824:/home/exploits/mjd$ exit
logout
References:
|
|
