I see that mailman/bin has a paths.py and paths.pyc that are set to 644
rather than 755 like everything else in bin. Changing them to 755 doesn't
solve my mailmanctl error problem. But were they installed with the right
perms? check_perms doesn't care about these files either way.
Whit
If I just comment out that paths line in mailmanctl, then it balks on the
next line with No module named Mailman. Same if I move the paths.py* files
from bin to Mailman and have the paths line be from Mailman import paths.
Could my installing mailman in /web/mailman rather than
Thanks Bruce.
I see that mailmanctl doesn't throw those errors if I start it from
/web/mailman/bin rather than /etc/init.d. (However, I still have a Site
list is missing: mailman error to sleuth out.) Where do you run mailmanctl
from? Have I missed something on setting a system variable in the
On Monday, July 28, 2003, at 07:37 pm, Whit Blauvelt wrote:
Thanks Bruce.
I see that mailmanctl doesn't throw those errors if I start it from
/web/mailman/bin rather than /etc/init.d. (However, I still have a
Site
list is missing: mailman error to sleuth out.)
Check out the INSTALL file in a
On Mon, Jul 28, 2003 at 08:34:32PM +0100, Richard Barrett wrote:
Where do you run mailmanctl from? Have I missed something on setting a
system variable in the INSTALL instructions, that would enable it to work
from /etc/init.d as advertised with mailman not installed in the default
