It looks to me like check_perms has a hole in it, Mark. If you take a close
look at the error I've been getting repeatedly since early July (see below),
you'll see it consistently occurs on the index.html table in the
/usr/local/mailman/archives/private/mylist directory. Here are the
permissions on that file:
12 -rw-r--r-- 1 mailman mailman 11452 Oct 20 07:01 index.html
Please note that the permissions on that file are 644 and not 664. I just
ran check_perms on this account. It reported "No Problems Found". Yet when
Archrunner runs and tries to open that file to replace it, it reports a
permissions error for that file. In short, check_perms reports those 644
permissions are just fine while you're telling me they should be 664 and
ARCHrunner complains they're NOT fine. This suggests to me check_perms isn't
doing its job very well.
Am I wrong about this?
Here's the error ARCHrunner has been reporting repeatedly since early
July...
Oct 28 10:09:30 2008 (2589) Uncaught runner exception: [Errno 13] Permission
denied: '/usr/local/mailman/archives/private/mylist/index.html'
Oct 28 10:09:30 2008 (2589) Traceback (most recent call last):
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop
self._onefile(msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/ArchRunner.py", line 73, in
_dispose
mlist.ArchiveMail(msg)
File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 217, in
ArchiveMa
il
h.close()
File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 324, in
close
self.write_TOC()
File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1097, in
write_T
OC
toc = open(os.path.join(self.basedir, 'index.html'), 'w')
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/archives/private/mylist/index.html'
What am I missing here?
-----Original Message-----
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 5:50 PM
To: [EMAIL PROTECTED]; mailman-users@python.org
Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the
archive process running?
TGPlatt, WebMaster wrote:
>
>Now can we talk about the proper ownership of all the mailman files both IN
>/usr/local/mailman directory structure and in the UserAccount/mailman
>directory as well? Shouldn't all (or most of) these files be owned by
>mailman / mailman? Is that also true in the /archives/private/mylist
>directory? What about over in the /home/mylist/www directory? Who should
own
>the mailman directory there?
>
>I have run bin/check_perms several times but it doesn't complain about any
>problems.
check_perms should complain about ownership and permission problems.
Assuming mailman's home directory is NOT /usr/local/mailman and
assuming that prefix, and var_prefix are /usr/local/mailman, mailman's
home directory is irrelevant.
In general everything from /usr/local/mailman on down should be group
mailman (owner doesn't matter) and directories need to be g+rws and
files g+rw.
See the post at
<http://mail.python.org/pipermail/mailman-users/2008-October/063748.html>.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
