[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Infomous Majordomo
- Subject: Re: [cobalt-users] Infomous Majordomo
- From: Jeff Lasman <support@xxxxxxxxxxxxx>
- Date: Tue Dec 21 00:54:36 1999
That one's easy <smile>...
From the Majordomo "Newlist" document (I don't think Cobalt supplies it):
> Finally, make sure everything is owned by user majordomo, group
> majordomo, and writable by both owner and group (i.e., mode 664 for
> files and mode 775 for directories.
Of course we don't want to change the owner and group (or do we?), but all
files under the lists directory should be mode 664, the lists directory
itself, and all directories under it should be 775.
I also added "mail" to the daemon group, since majordomo appears to run as
"mail" (see below).
Of course then you'll probably get:
chown(110, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted
when you try an unsubscribe...
This is what I get <frown>.
The problem is in line 435 of the "majordomo" file,
chown($uid, $gid, "$listdir/$clean_list.new") ||
&abort("chown($uid, $gid, \"$listdir/$clean_list.new\"): $!");
User 110 is admin. Group 2 is daemon.
Okay, majordomo is creating the file (in line 431) with ownership "mail:mail".
That's reasonable; majordomo is probably running as mail (as the error
message you get would have you believe, since UID 8 is mail and GID 12 is mail.
But then how come it tries to change it to admin:daemon?
So web administration can manipulate it? This is the only reason I can
think of <frown>.
I'm still working on this one, and have an open case with tech support on
which I'm awaiting a phone call <frown>.
(Majordomo is pretty dumb. It doesn't know how to remove a line from a
file. So this is what it does: It creates a new empty file, listname.new.
Then it copies over one line at a time from listname to listname.new
(except for the line it wants to delete, of course).
Then it removes listname and renames listname.new as listname.
Jeff
At 08:19 PM 12/14/99 Kevin wrote:
I have verified all directory and file permissions with another RAQ2.
This appears to be my main error. Does anyone have any idea what to do?
shlock: '/usr/local/majordomo/lists' is not writable by UID 8 GID 12
--
nobaloney.net Customer Support
<support@xxxxxxxxxxxxx>
<www.nobaloney.net>