Richard,
You were absolutely right. There was an error in the uid/gid mappings. But
I believe that's out of the way now since now I get other errors. *sigh* It
never ends! Maybe I'd kill the .rpm install and do one from scratch
instead.
Traceback (most recent call last):
File "/usr/lib/mailman/cron/gate_news", line 40, in ?
from Mailman import MailList
File "/usr/lib/mailman/Mailman/MailList.py", line 36, in ?
from Mailman import Utils
File "/usr/lib/mailman/Mailman/Utils.py", line 45, in ?
from Mailman import Crypt
File "/usr/lib/mailman/Mailman/Crypt.py", line 19, in ?
if mm_cfg.USE_CRYPT:
AttributeError: 'module' object has no attribute 'USE_CRYPT'
And then in next mess I get:
/usr/bin/python: can't open file '/usr/lib/mailman/cron/senddigests'
And:
/usr/bin/python: can't open file '/usr/lib/mailman/cron/gate_news'
Anders Norrbring
Norrbring Consulting
-> Then I guess you will have to check what uid/gid has write permissions
-> over the /var/lib/mailman/locks/ directory and compare this for
-> compatibilty with the uid that the Mailman crontab has been installed
-> under.
->
-> I would expect then both to be the 'mailman' uid (as decided by the
-> installer when Mailman was configured) but plainly they cannot be
-> compatible or you would not have a permissions failure when the cron
-> job is (presumably) trying to create a lock file in the directory.
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
