>>> Dave Wolfe <dwolfe@risc.sps.mot.com> - 8/29/95 8:37 AM >>>
I'm not sure how you got the impression that the FAQ just says the
Log file must be readable. In fact, it and the directory it resides
in must be *writable* by user majordomo:
I GET "OUT OF MEMORY" WHEN UPGRADING TO 1.93
[summary of report from Matthew A. Braithwaite]
There appears to be a bug in error reporting in Majordomo 1.93.
Under
certain circumstanses [sic], if the directory containing your Log
file is
not writeable by majordomo then it will get caught in an infinite
recursion, eventually allocating all the memory in the system. The
fix
is to make sure that the directory containing your Log file is
user
and group writeable, and user and group owned by your majordomo
user
and group. This doesn't work in all cases. There have been reports
that some O/S have bugs in Perl's eval() routine causing this
error.
This condition will also arise if the wrapper is configured and
installed [im]properly. Refer above for how to configure and
install the
wrapper on your system.
<<<<<<
Whoops, my mistake. I meant to say I *did* make the log file and its
directory readable and writable by the majordomo group and user
(actually, the user is majordom).
The wrapper appears to work fine (it passes the test). It could be
Perl, though I just installed Perl 5.001.
I'll look at the wrapper again, though if anyone else has any ideas,
I'd love to hear them. I'm not a Perl expert, so I'll take any help
I can get in debugging this problem.
Wade Williams
wwilliams@mail.state.tn.us
|
|
