> majordomo's listdir is /usr/lists. within that directory, each directory
> has its own directory, in which the subscription and config files are
> kept. ie:
>
> /usr/lists majordom.lists drwxr-x--x
> /usr/lists/example tj.lists drwxrws---
> example tj.lists -rw-rw----
> example.config tj.lists -rw-rw----
>
I would think that doing the opposite of what you have attempted would
prove better suited for the situation.
Rather than changing the owner affiliation (and thus breaking majordomo),
leave all list files owned by majordomo and change the group ownership.
Of course this involves adding a new, unique group for each user/list
combination but it should work much better...in theory anyway.
I haven't tried it but it seems reasonable that the only real reason
majordomo has for complaining right now is the fact that it doesn't own
the files its trying to write to.
I thought this had been done on one of the systems I maintain, locally, a
list on but it turns out that the admin just made the file world write and
read...I would not suggest this.
Anyone else know whether or not this will work better?
____________________________
Mike Neuharth
ADCS Technology Specialist
http://www.umn.edu/adcs
E-Mail : mjn@umn.edu
Page Mail : 6126486512@page.metrocall.com
http://nifty.dsl.visi.com/
____________________________
References:
|
|
