I'm afraid it doesn't - here's an example:
[root@unica mailman]# ls -lR lists/|grep config.db
-rw-rw1 nobody mail 9759 May 9 14:14 config.db
-rw-rw1 nobody mail 9759 May 9 14:14 config.db.last
-rw-rw1 mailman mail16876 May 9 15:27 config.db
Apparently you didn't read what I said.
> -rw-rw1 nobody mail16875 May 8 18:16
> /home/mailman/lists/thelist/config.db
is not group mailman. That would be the problem, and I have to believe
that check_perms would find it, too.
> > The web server writes it. This is not a pro
Actually it does present a problem because this is the error it generates:
May 08 18:26:01 2001 qrunner(7593): Traceback (most recent call last):
May 08 18:26:01 2001 qrunner(7593): File "/home/mailman/cron/qrunner", line
278, in ?
May 08 18:26:01 2001 qrunner(7593): kids = main(lock)
May
> For some reason, the config.db file of the list previously in question keeps
> being set to an ownership of 'nobody'. help?
The web server writes it. This is not a problem, because it's owned
by group mailman, and write permissions are granted to group mailman.
-
For some reason, the config.db file of the list previously in question keeps
being set to an ownership of 'nobody'. help?
Tib
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
