> > check_perms should be finding all this; you need to find out what's going
> > wrong with check_perms.
>
> I tested with changing permissions/ownerships around on a few things
> to see what check_perms would and would not catch, and found an
> something interesting: Check_perms wants to set
On Wed, 9 May 2001, Dan Mick wrote:
> Doublecheck your version of check_perms; the code is there, and it
> works, in 2.0.5. Are you running check_perms from the installed
> bin/ directory as the instructions and about a billion posts on this
> list say?
Yes. I did.
> check_perms should be find
Tib ([EMAIL PROTECTED]) said something that sounded like:
> [root@unica mailman]# ls -lR lists/|grep config.db
Are the directories set-gid? This will help in some cases where things
are not ran through a set-gid program. Make sure that they are set to
be 2775 (drwxrwsr-x).
Ciao,
--
Pug Bainte
> Check_perms fails to find it, and it's turning into a major problem.
Doublecheck your version of check_perms; the code is there, and it
works, in 2.0.5. Are you running check_perms from the installed
bin/ directory as the instructions and about a billion posts on this
list say?
> What (exac
Check_perms fails to find it, and it's turning into a major problem.
What (exactly) writes and rewrites the config.db file and what are the actual
permissions it's supposed to have? From ealier reference it sounded as though
it should be owned by nobody (since the webserver
modifies/creates/backs
