I experienced the same problems with our majordomo here. Problem was there's
about 20 list administrators who access the lists directly via telnet..
Problem is when they save the file after adding or delting the ownerships
would be wrong and then majordomo would abort because it did not have
ownership of the file. I got around this by making a script that basically
chown's the list directory every 5 minutes..
My fix-lists file (make sure you chmod 755 it) I put it under
/usr/majordomo-1.94.5/bin you can put it where ever you want just make sure
you call it out right in the crontab file. (Also note to place YOUR corect
user and group in place of majordom.nofiles)
# ! /bin/sh -
chown -R majordom.nofiles /usr/majordomo-1.94.5/lists
Then I setup my crontab file to run that script every 5 minutes as root.
You can find the crontab file under /etc I might be off a * though as I'm
speed typing this.
5/* * * * * root /usr/majordomo-1.94.5/bin/fix-lists
If you don't want a message from your server every 5 minutes that it's
executed the script then just leave the root off the abouve example. It will
still chown the directory but won't send you an email every 5 minutes.
--JT
----- Original Message -----
From: "mjn" <mjn@umn.edu>
To: "Robin Sanders" <sanders@math.buffalostate.edu>
Cc: <majordomo-users@GreatCircle.COM>
Sent: Friday, February 23, 2001 12:06 PM
Subject: Re: People can't get OFF my l*sts
As of Feb 23, 2001, Robin Sanders can be held liable for saying:
> First, thanks to the helpful souls who let me know how to
> post this.
>
> I'm using majordomo 1.94.5 on a RedHat 6.2 system to manage a
> small number of departmental lists. My students and faculty
> members can s_bscribe and post to the lists without any
> problem.
>
> But everytime someone attempts to "uns_bscribe" to a list, I
> get the following error message bounced back to my account
> (as the majordomo caretaker):
>
> >
> > MAJORDOMO ABORT (mj_majordomo)!!
> >
> > chown(851, 12, "/usr/local/majordomo-1.94.5/lists/mat164.new"):
Operation not permitted
> >
>
> Any ideas on what this means? This happens even when there is no
> *.new or L.* file in my lists directory.
>
> Any ideas on how to fix the problem?
>
> By the way, majordomo has UID 851 and the group "mail" has GID 12.
>
Robin-
Is /usr/local/majordomo-1.94.5/lists owned by the majordomo user?
Looks to me like majordomo does not have create/write permissions in your
lists directory...
____________________________
Mike Neuharth
ADCS Technology Specialist
http://www.umn.edu/adcs
E-Mail : mjn@umn.edu
Page Mail : 6126486512@page.metrocall.com
http://supermonkeycollider.dyndns.org/
____________________________
|
|
