On 2015-9-22 17:16 , Steffen Kaiser wrote:
> I had SpamAssassin rules allocating about 100MB, the forked children
> only shared the C libraries after some time. That's a problem of
> Perl's way to handle rereferences to data.
It might help not to integrate SpamAssassin, but to use spamc to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 22 Sep 2015, Amit Gupta wrote:
My situation is that the number of mimedefang.pl processes jumps to
about 70 during peak loads (we are processing a couple hundres
messages per minute on average). Our filter file is in need of some
Apologies for starting a new thread. I couldn't find any messages in
my inbox to reply to.
Thanks Paul, Bill and Diane for your replies.
My situation is that the number of mimedefang.pl processes jumps to
about 70 during peak loads (we are processing a couple hundres
messages per minute on
On Tue, 22 Sep 2015 07:57:18 -0700
Amit Gupta wrote:
> My situation is that the number of mimedefang.pl processes jumps to
> about 70 during peak loads (we are processing a couple hundres
> messages per minute on average).
How much RAM do you have? 70 parallel scanners is
We have 16GB of ram, though there are other processes running on this
machine such as DB that will be segmented later. I'm curious how much
resident memory each of your mimedefang.pl processes uses? I haven't
been tracking my mimedefang.pl memory usage over time, so I was a
little surprised to
On Tue, 22 Sep 2015 08:20:16 -0700
Amit Gupta wrote:
> We have 16GB of ram, though there are other processes running on this
> machine such as DB that will be segmented later. I'm curious how much
> resident memory each of your mimedefang.pl processes uses?
About 110MB, but
On 21 Sep 2015, at 17:04, Amit Gupta wrote:
Hi, I'm using Centos7.1 and mimedefang 2.75 (still need to upgrade to
latest). The documentation indicates that if you start mimedefang with
the -E parameter, it uses embedded perl which is supposedly faster. I
was wondering if someone could give me
On Mon, 21 Sep 2015 18:53:04 -0400
"Bill Cole" wrote:
> As MD & Perl have matured and systems have gotten much bigger and
> much faster it has become less of a burden to just fork and exec
> fully independent slaves and let them live a very long time, so
On Mon, 21 Sep 2015 14:04:04 -0700
Amit Gupta wrote:
> Hi, I'm using Centos7.1 and mimedefang 2.75 (still need to upgrade to
> latest). The documentation indicates that if you start mimedefang with
> the -E parameter, it uses embedded perl which is supposedly faster. I
> was
Hi, I'm using Centos7.1 and mimedefang 2.75 (still need to upgrade to
latest). The documentation indicates that if you start mimedefang with
the -E parameter, it uses embedded perl which is supposedly faster. I
was wondering if someone could give me insight into why it's actually
faster under the
...@lists.roaringpenguin.com] On Behalf Of Amit
Gupta
Sent: Monday, September 21, 2015 2:04 PM
To: mimedefang@lists.roaringpenguin.com
Subject: [Mimedefang] Embedded Perl
Hi, I'm using Centos7.1 and mimedefang 2.75 (still need to upgrade to
latest). The documentation indicates that if you start mimedefang
On Mon, 18 Jun 2012 19:19:57 +0900
Nathan Findley nat...@zenlok.com wrote:
The man pages for the multiplexer indicate that when using embedded
perl the PID of the slave is not available ($$). Is there a way
around this?
Wow, that man page is way out of date. :) I fixed that many versions
of
Kayne Kruse wrote:
Now Take david, hes a rather nice person. Now that I said that, why do
you support this monstrosity? :) That was some hideous code, makes me
want to puke shellcodes in the morning! :D Anywho, note taken and I
yanked that crap out.
In fact, I'd never looked closely at
On Thu, 2006-07-20 at 10:03 -0400, David F. Skoll wrote:
In fact, I'd never looked closely at File::Scan before.
I have removed support for File::Scan from MIMEDefang completely; the
next release won't support it. If you want to continue to use it, you'll
have to write the supporting code
::snip::
Only reason I had it to begin with was as an extra scanner.
Call me paranoid, but the cost of two scanners is worth the
cpu time just to be extra safe.
We killed-off File::Scan several months ago, when it was corrupting PDF
files from some of our production batch jobs, depending upon
On Thu, 2006-07-20 at 10:03 -0400, David F. Skoll wrote:
I can't in good
conscience have built-in support for such a terrible module.
Regards,
David.
Ironically, I think this has been the cause of my hanging mimedefang i
hadnt posted about. Watching the logs I dont appear to have any
- Original Message -
From: Kayne Kruse [EMAIL PROTECTED]
To: mimedefang@lists.roaringpenguin.com
Sent: Thursday, July 20, 2006 3:36 PM
Subject: Re: File::Scan (was Re: [Mimedefang] Embedded Perl
multiplexoronDebian - sarge Error)
___
NOTE
I just noticed this error, and was curious as to what in the filter is
the FD.
Jul 19 17:03:02 mailfilter mimedefang-multiplexor[4711]: WARNING:
Something in your Perl filter appears to have opened a file descriptor
outside of any function. With embedded Perl, you should move any code
that opens
Kayne Kruse wrote:
I just noticed this error, and was curious as to what in the filter is
the FD.
Jul 19 17:03:02 mailfilter mimedefang-multiplexor[4711]: WARNING:
Something in your Perl filter appears to have opened a file descriptor
outside of any function. [...]
lr-x-- 1 root root
Remove File::Scan from your system. It's buggy and evil.
Regards,
David.
Now Take david, hes a rather nice person. Now that I said that, why do
you support this monstrosity? :) That was some hideous code, makes me
want to puke shellcodes in the morning! :D Anywho, note taken and I
Hi all,
I just tried 2.45 out and found out that MD 2.45 is not able to reload
embedded perl slaves anymore. I've tracked it down to:
+(eval 'use Net::DNS; $Features{Net::DNS} = 1;')
+or $Features{Net::DNS} = 0;
This module seems to specify a var which is used somewhere else
(namespace
+(eval 'use Net::DNS; $Features{Net::DNS} = 1;')
+or $Features{Net::DNS} = 0;
After looking at Net::DNS I suspect that a circular reference is the problem
here.
I dunno how to solve it.
Martin
___
Visit http://www.mimedefang.org and
Hi,
We have just noticed a bit of weirdness with embedded Perl. If you
use an embedded Perl interpreter, the Perl $$ variable does not
reflect the process ID of each slave. Instead, it continues to hold
the process ID of the master multiplexor.
I've looked into the Perl source code and
Chris Gauch said:
The embedded perl interpreter definitely minimizes the memory usage by the
MD slaves, but I don't really notice an overall improvement in total
memory
usage when using the embedded perl option. All 1.5GB of RAM is still used
up entirely, and I have the same number of
duh,
didn't see any of the previous posts, until just now.
I guess I never do a reread, always a restart, that would explain why I
never saw the error.
Dave,
Should the default mimedefang-filter have use strict in it, in the
default install?
Would that solve some problems?
--
Luke Computer
Hi,
Should the default mimedefang-filter have use strict in it, in the
default install?
Would that solve some problems?
It can fix some unpropper written code which makes troubles in the
reload szenario ...
Martin
___
Visit
From: Martin Blapp [mailto:[EMAIL PROTECTED]
Should the default mimedefang-filter have use strict in it, in the
default install?
Would that solve some problems?
It can fix some unpropper written code which makes troubles in the
reload szenario ...
*ALL* production Perl code should live
:15 AM
To: [EMAIL PROTECTED]
Subject: RE: [Mimedefang] MIMEDefang embedded perl stability issues
On Fri, 25 Jun 2004, Chris Gauch wrote:
Yep -- just realized that -- see my previous email about doing a
mimedefang
reread in a cron.daily script. Hopefully removing that reread command
will
fix
A couple weeks ago I opted to use the MIMEDefang embedded perl interpreter
(by turning on MX_EMBED_PERL=yes in the MD init script), however, I have
noticed some stability problems when using the embedded interpreter. Every
morning at 5am the MD multiplexor essentially craps out, requiring
On Fri, 25 Jun 2004, Chris Gauch wrote:
A couple weeks ago I opted to use the MIMEDefang embedded perl interpreter
(by turning on MX_EMBED_PERL=yes in the MD init script), however, I have
noticed some stability problems when using the embedded interpreter. Every
morning at 5am the MD
perl stability issues
On Fri, 25 Jun 2004, Chris Gauch wrote:
A couple weeks ago I opted to use the MIMEDefang embedded perl interpreter
(by turning on MX_EMBED_PERL=yes in the MD init script), however, I have
noticed some stability problems when using the embedded interpreter.
Every
morning
Hi,
noticed some stability problems when using the embedded interpreter. Every
morning at 5am the MD multiplexor essentially craps out,
We had the same issue. We found that unproper handling with global variables was
the cause.
So use 'use strinct' in mimedefang-filter and be careful with
I would check your crontab to see what is running at 5AM. This sounds more
like the box running out or ram or something.
A couple weeks ago I opted to use the MIMEDefang embedded perl interpreter
(by turning on MX_EMBED_PERL=yes in the MD init script), however, I have
noticed some stability
I would check your crontab to see what is running at 5AM. This sounds more
like the box running out or ram or something.
Are you doing a mimedefang reload at this time ?
Martin
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang
A.
McGrail
Sent: Friday, June 25, 2004 10:24 AM
To: [EMAIL PROTECTED]
Subject: Re: [Mimedefang] MIMEDefang embedded perl stability issues
I would check your crontab to see what is running at 5AM. This sounds more
like the box running out or ram or something.
A couple weeks ago I opted to use
, 2004 10:34 AM
To: [EMAIL PROTECTED]
Subject: Re: [Mimedefang] MIMEDefang embedded perl stability issues
I would check your crontab to see what is running at 5AM. This sounds
more
like the box running out or ram or something.
Are you doing a mimedefang reload at this time ?
Martin
* Chris Gauch [EMAIL PROTECTED]
I'm on Redhat Linux 9 for the OS, latest kernel, etc. (through RHN
update). MIMEDefang version is 2.43, Spamassassin 2.63, and ClamAV
0.72. This problem was fairly consistent when using the embedded perl
interpreter, the MD multiplexor would crash at almost the
Yeah, you might want to tail -f your maillog and then do a reread and see if
your mimedefang is even capable of a reread on your platform with embedded
perl. It is not on mine.
Regards,
KAM
The only item of doubt is a rulesdujour script that runs in cron.daily --
this updates a number of my
Yep -- just realized that -- see my previous email about doing a mimedefang
reread in a cron.daily script. Hopefully removing that reread command will
fix the issue!
Hi,
We had exactly the same issue.
Add:
use strict;
to your mimedefang filter and the problem will stop after you have
On Fri, 25 Jun 2004, Chris Gauch wrote:
Yep -- just realized that -- see my previous email about doing a mimedefang
reread in a cron.daily script. Hopefully removing that reread command will
fix the issue!
Could you see if 2.44-BETA-1 fixes it? I applied a patch from Martin
Blapp:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Add:
use strict;
to your mimedefang filter and the problem will stop after you
have fixed all
the error messages.
This is not true in all cases. This is the same problem I'm having. I
can't do a reread. I've been using use strict in my
Hi,
This is not true in all cases. This is the same problem I'm having. I
can't do a reread. I've been using use strict in my filter as long
as I remember.
Have run run mimedefang.pl -f mimedefang-filter /tmp as test ? Are there
still any warnings ?
Martin
Hi All,
Appologies if this is too far OT.
I'm 'use'ing some perl modules from within my
mimedefang-filter script.
I've just tested the embedded perl option and they
don't seem to be functioning properly. The first
module (Net::LDAP) that gets used doesn't function
properly (cannot establish
Chris Masters wrote:
I've just tested the embedded perl option and they
don't seem to be functioning properly. The first
module (Net::LDAP) that gets used doesn't function
properly (cannot establish connections).
If I change back to normal [non-embedded] mode it's
fine.
Are there any
--- Michael Sims [EMAIL PROTECTED] wrote:
Chris Masters wrote:
I've just tested the embedded perl option and they
don't seem to be functioning properly. The first
module (Net::LDAP) that gets used doesn't function
properly (cannot establish connections).
If I change back to normal
On Wed, 5 May 2004, Chris Masters wrote:
Hmmm. I initialise all connection handles in a
getConnection function that checks the connection and
opens one if necessary (because there never used to be
a filter_initialize function and it's very resilient).
Any other reasons?
We've noticed a
--- David F. Skoll [EMAIL PROTECTED] wrote:
On Wed, 5 May 2004, Chris Masters wrote:
Hmmm. I initialise all connection handles in a
getConnection function that checks the connection
and
opens one if necessary (because there never used
to be
a filter_initialize function and it's very
On Fri, 23 Apr 2004, Henrik Schmiediche wrote:
How can you test if a given implementation is safe?
Look at configure.in and search for
AC_MSG_CHECKING([if it is safe to destroy and recreate a Perl interpreter])
Does Perl need to be compiled in any special way to enable embedded Perl to
work?
On Sat, 2004-04-24 at 09:10, David F. Skoll wrote:
Yes; you need either a shared library libperl.so, or a static one (libperl.a)
on your system.
Would you have a lot of unnecessary overhead if, instead of
writing your own multiplexing and embedded perl, you ran
a stock apache/mod_perl or
On Fri, 23 Apr 2004, David F. Skoll wrote:
On Fri, 23 Apr 2004, Henrik Schmiediche wrote:
What is the advantage to Embedding Perl in the muliplexor?
Faster startup time and much less memory use.
The man mimedefang-multiplexor man page says:
-E Specifies that the multiplexor should
On Sat, 24 Apr 2004, Les Mikesell wrote:
Would you have a lot of unnecessary overhead if, instead of
writing your own multiplexing and embedded perl, you ran
a stock apache/mod_perl or fastcgi and a really simple
front end that dispatches the jobs via http requests?
I have no idea, and I
On Fri, 23 Apr 2004, Henrik Schmiediche wrote:
What is the advantage to Embedding Perl in the muliplexor?
Faster startup time and much less memory use.
Why is it not enabled by default?
Because it's broken on some platforms. It's fine on Linux,
mostly fine on Solaris 9, and all bets are off
, April 23, 2004 5:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [Mimedefang] Embedded perl
On Fri, 23 Apr 2004, Henrik Schmiediche wrote:
What is the advantage to Embedding Perl in the muliplexor?
Faster startup time and much less memory use.
Why is it not enabled by default?
Because it's broken
I think that I've found and fixed a problem in MIMEDefang's embedded
Perl mode.
The problem: The MIMEDefang multiplexor uses the openlog and syslog
functions to write to the syslog. These functions use a file descriptor
kept in a static variable somewhere to do the actual writing. However,
Lucas Albers wrote:
You should show this sort of command arguments when you run
ps axuww|grep mimedefang
/usr/bin/mimedefang-multiplexor -p
/var/spool/MIMEDefang/mimedefang-multiplexor.pid -E -m 4 -x 9 -U defang -i
30 -b 600 -W 1 -l -q 10 -s
/var/spool/MIMEDefang/mimedefang-multiplexor.sock
Verify it is using the newer embedded version by calling manually.
what is the full memory listing for all the mimedefang process?
post the result of ps axuww | grep mimedefang
cut off parts so it doesn't word wrap.
Josh Kelley said:
I've verified that the -E is listed in the ps auxwww listing,
I'm trying to get the multiplexor's embedded Perl mode to work, since
messages on the mailing list indicated that it would save a lot of
memory, and our mail server (running Red Hat Enterprise Linux 3) is a
bit limited on memory.
First, a minor point: it doesn't seem to be helping the memory
Josh Kelley said:
I'm trying to get the multiplexor's embedded Perl mode to work, since
messages on the mailing list indicated that it would save a lot of
memory, and our mail server (running Red Hat Enterprise Linux 3) is a
bit limited on memory.
First, a minor point: it doesn't seem to be
Lucas Albers wrote:
What version of perl are you running?
5.8.0, the version that ships with RHEL 3.
Look at the shared memory, it will indicate that each slave is sharing 2/3
of it's memory with the master.
Like such:
defang 9 0 31992 31M 19972 S 0.0 6.3 0:00 mimedefang-mult
Josh Kelley said:
I'm using the provided init script for Red Hat, so I can set the
appropriate option in /etc/sysconfig/mimedefang to make the init script
pass the -E option.
I've confirmed that ps lists the children as mimedefang-multiplexor
rather than perl mimedefang.pl, which should
60 matches
Mail list logo