On Fri, Apr 27, 2001 at 05:09:45PM -0400, Daniel Einspanjer wrote:
> Fortunately, it is no longer the standard hard link problem. :) I read
> the FAQ and the README.LINUX and ran the secure_linux fix. One thing that
> took me a bit to figure out is that you have to run that script with a
move_list did in fact fix my problem.
Some notes to anyone in the future running into problems with move_list, make sure you
clear out any stale lock files before you run it. It will just sit and wait for the
locks to clear if you don't.
Daniel
On Fri, 27 Apr 2001 15:13:22 -0600, Ashley M. K
Daniel Einspanjer wrote:
> I tried that, but the move_list program hangs as well. I can only assume it is
>reading that bad directory and failing?
> I'm going to try to create a symlinked structure and see if it can run then. Any
>further ideas would be greatly appreciated.
Synlinks have
I tried that, but the move_list program hangs as well. I can only assume it is
reading that bad directory and failing?
I'm going to try to create a symlinked structure and see if it can run then. Any
further ideas would be greatly appreciated.
Daniel
On Fri, 27 Apr 2001 15:13:22 -0600, Ashl
Daniel Einspanjer wrote:
> I think I found the problem. I didn't make a mailman user in my new installation,
>used my existing user "mail" and set up a /home/mail/ directory. Unfortunately, when
>doing a grep for "/home/mailman/", I see the the mailing list's config.db is still
>pointing to
I think I found the problem. I didn't make a mailman user in my new installation,
used my existing user "mail" and set up a /home/mail/ directory. Unfortunately, when
doing a grep for "/home/mailman/", I see the the mailing list's config.db is still
pointing to the old directory structure. C
I'm having a problem with mailman 2.04 running with exim and apache on a mandrake
distro.
Fortunately, it is no longer the standard hard link problem. :) I read the FAQ and
the README.LINUX and ran the secure_linux fix. One thing that took me a bit to figure
out is that you have to run that
