12-11-96
Majordomo 1.94 on my FreeBSD Perl5.003-based system is doing extremly
odd things.
Here is some sample output from the majordomo.debug file:
Out of memory!
Out of memory!
Out of memory!
Attempt to free unreferenced glob pointers, <> chunk 1.
After adding $DEBUG = 1; to the cf file, I got a MASSIVE listing of the
following information repreated over and over again:
/usr/local/majordomo/majordomo: main'log()
/usr/local/majordomo/majordomo: main'log(): opening logfile
/var/log/majordomo.log
/usr/local/majordomo/majordomo: main'log()
/usr/local/majordomo/majordomo: main'log(): opening logfile
/var/log/majordomo.log
Out of memory!
The permissions on all the files (including the log file in /var/log) are
set correctly. Thec config-test scripts works, ie., if I run it as
myself I get my uid/gid and environmental settings, if ./wrapper config-test
is run, the uid/gid of majordomo (which is listserv.daemon) is in the
output. Also, listserv, the majordomo user, is a trusted user as far as
sendmail 8.8.3 is concerned. Point of clarification, the directories are
775 and the log files are 664. EVERYTHING is owned by listserv.daemon except
the wrapper.
Furthermore, wrapper was configured for a POSIX-compliant system since
FreeBSD IS a POSIX-compliant system. I tried to compile the wrapper for
non-POSIX systems, and FreeBSD cried foul. That is, I got a message
saying that I need to recompile the wrapper.
All of the @ characters in the majordomo and majordomo.cf files are escaped
properly. And Perl seems VERY happy with everything else. However, with
Majordomo 1.94, I get a perl.core file generated and a memory leak error
mailed to root. You can actually see the memory leak in action: Perl
begins as a 2 meg resident program and it LEAPS to a 64 M program while
interpreting the majordomo scripts.
Anyone got any ideas about what could be wrong here? The only test I have
done is to set up the MOST basic aliases and create a test list in
/usr/local/var/lists. I mail "lists" to majordomo, and I get the errors
that I have mentioned.
Thanks in advance,
Josh Pincus
Follow-Ups:
|
|
