Lo and behold, Glacier Sys-Amin once said:
>
> Hey everyone!! I'm running Linux, and I couldn't get Majordomo to work
> with perl 5.000-anything, so I went back down to 4.036, and it's much
> better now!!
I'm runing Linux as well, and Majordomo works like a charm under Perl
5.001e. My bet is that if you're running anything after this version,
it's not perl that's at fault.
> See I did the test example and it actually worked, but I almost CRASHED
> my system doing it. I have 48 Megs of RAM, and 48 Megs of SWAP space,
> and I think that it ate it all up!!!!! My whole system came to a serious
> crawl, and my hard drive went crazy. I killed the processes that were
> huge, and found that it actually worked.
> Could someone please help me from running out of memory?? I mean, I
> understand that mailing lists can take up some resources, but you know,
> this is only (1) message. If I get 2 users, at this point, I'll be
> doomed. :)
I realize it's strange, but this problem is addressed in the FAQ, and
the FAQ is right. :) What the FAQ doesn't mention is a strange little
twerpy linux-specific thing about permissions. (At least, this is the
problem I was having).
1) Check the permissions on *all* of your files and directories. This
problem, imho and in the faq is often related to majordomo not being able
to open the logfile. All files should be read/writable by owner and
group (majordom.majordom if you're using the std. stuff).
2) Check the permissions on the *parent* directories of the majordomo
stuff. They should all be at least WORLD executable. (chmod +x). They
don't need to be readable, but all directories in the path up to your
majordomo files must be executable. This one drove me nutso for a while
until I got it.
3) Pray? :)
Best of luck with it. :)
--Dave Andersen
---
angio@aros.net (webmaster/sysadmin)
>
|
|
