[Mimedefang] Embedding Perl in Multiplexor -- good idea?

[Cormack, Ken]

If I understand correctly, the proposed change means I essentially have to
bounce the multiplexor, which means I have to bring down sendmail, to effect
any new rules?

I'd ask that things remain the same, or be an admin-selectable behavior, if
possible.

Ken

-----Original Message-----
From: David F. Skoll [mailto:dfs at roaringpenguin.com]
Sent: Wednesday, October 22, 2003 3:54 PM
To: mimedefang at lists.roaringpenguin.com
Subject: [Mimedefang] Embedding Perl in Multiplexor -- good idea?


Hi,

Currently, the multiplexor has a function called activateSlave which
(more-or-less) does a fork(), some fooling around with pipes, and
then an exec() of "perl mimedefang.pl"

Another option is to embed the Perl interpreter directly in the
multiplexor so all the initialization is done _once_.  Then
activateSlave() only needs to do the fork() and pipe-manipulation.

The downside is that if you change your filter, you have to kill and
restart the multiplexor, instead of just telling it to terminate and
restart slaves at its earliest convenience.

Good idea?  Pros?  Cons?  Will it make enough of a difference seeing as
we already amortize Perl startup costs over a few hundred messages?

--
David.
_______________________________________________
MIMEDefang mailing list
MIMEDefang at lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang