[ Lee McKusick writes: ]
>
> Here is a bug report and a request for a bit more troubleshooting
> documentation.
Contributions are always appreciated. ;-) One thing you should realize,
however, is that development has stopped on 1.9x because 2.x in under
development. And documentation for Mj2 is even more appreciated.
> I installed majordomo-1.94.4-6.i386.rpm on my RedHat Linux 5.2 system.
> The supplied perl-5.004m4-1.i386.rpm fails to correctly process "here
> documents".
>
> Replacing the perl program with perl5.005_02 (straight off the
> internet) removes the problem.
>
> In short, perl version 5.004_04 should be listed in the FAQ as a
> problem.
No, the Linux Perl RPM is the problem. 5.004_04 works just fine, it's
what I'm using for all my Mj 1.94.4 installations, including Linux, but
I built Perl myself. The problem is whoever packaged that RPM had a bad
compiler or something.
> One: tell users how to turn on DEBUG (I saw it, I couldn't figure out
> how to turn it on).
The non-obvious part is that the debug log files must be created as
well IF, and only if, the debug log security patch is applied, which it
is in the Linux RPM. The security test for linked files fails when the
files don't exist. FTR, the easiest way to enable debugging is to create
the necessary file(s) in the $TMPDIR directory (be sure they have the
proper ownership and permissions) and add an appropriate line(s) to your
majordomo.cf, e.g.:
$DEBUG = 1 if $program_name eq 'mj_majordomo';
Making it conditional on the program_name allows one to selectively
enable debug without getting drowned in output from other parts of
Mj. Remember that $TMPDIR and the debug log files shouldn't be world
readable (and certainly not world writable!) to maintain security.
> Two: How to test majordomo separately from the wrapper. Could I
> simply send majordomo a test file on the command line and watch the
> stdout?
Mj depends on its environment and the current directory. Testing it
under any other conditions doesn't make sense. The wrapper ensures that
the conditions are correct no matter what uid started it. But to answer
your question, no, nothing is output to stdout, it's not an interactive
program and 1.9x versions don't have an interactive mode.
> Three: Maybe a bit more clarification on what is the simplest
> possible input to majordomo and what is supposed to come out.
A mail message and the e-mailed response, respectively. Try this:
echo help | /usr/lib/sendmail -v majordomo
That just gives you the verbose output from sendmail but it verifies
that sendmail can deliver to your majordomo alias. You should receive,
in your mailbox (actually the mailbox of the logged in user), Mj's help
message. Substitute any other Mj command you wish.
--
Dave Wolfe
References:
|
|
