>>>>> "MM" == Michael Martinez <firstname.lastname@example.org> writes:
MM> How do you get it to know about these variables?
You don't. Or I suppose you could, but what difference would it make? You
would eliminate one warning (not error, but warning) from the config
checker. It would have zero effect on the operation of Majordomo. None
whatsoever. config-test just goes through and looks for variables defined
in majordomo.cf; if it sees any that it doesn't know about, it warns. If
it doesn't see some that are important, then it spits out errors.
Variables that are there which it doesn't know about pose no problem
whatsoever, but might indicate typos or something so it's courteous and
tells you about them.
MM> I don't know perl. I don't know why these particular two variables do
MM> not work.
You aren't describing what you mean by 'not work'. So far all I've see is
that config-test told you it didn't know about them, which isn't really
much of anything.
You're a system administrator; surely you understand that for us to solve
any of your problems you have to provide complete information on exactly
what you did, what you expected to happen, what actually did happen and
full details of your system. Didn't we go through this on your last issue?
Things would be so much simpler if you would assist us just a bit; with
complete information we could just provide you with answers instead of
going back and forth.
MM> The effect is rather severe: sendmail cannot fork because of lack of
MM> resources, which results in no messages getting sent out.
And why are you running out of resources?
All I've managed to guess at so far is that you're running a lot of list
traffic on a slow machine or something and that you want to shut majordomo
down when the load gets high. So you uncommented the example code in
majordomo.cf. That does is commented out for a reason; you need to
understand what it does and how to make it work on your system. It
probably won't "just work".