And that no amount of training will fix it once it goes bad. I was
getting maybe 30-40 spams through
every day and many of them marked BAYES_00 -- and the last month I've
been carefully feeding the
software spam and ham lists, all carefully checked, but so much of it
just kept coming in.
But
On 10/20/2012 5:01 PM, Jari Fredriksson wrote:
Sa-compile says:
# /usr/bin/sa-compile
Oct 20 23:59:32.992 [6734] info: generic: base extraction starting. this
can take a while...
Oct 20 23:59:32.992 [6734] info: generic: extracting from rules of type
body_0
100%
[
Sa-compile says:
# /usr/bin/sa-compile
Oct 20 23:59:32.992 [6734] info: generic: base extraction starting. this
can take a while...
Oct 20 23:59:32.992 [6734] info: generic: extracting from rules of type
body_0
100%
[
Am 20.10.2012 14:52, schrieb Alexandre Boyer:
> I used monit in the past and had very nasty behaviors, multiple
> instances of the same process running. May be monit is better know.
i use monit since years with no bigger problems, but for sure
i do not use config examples, i edited them for my nee
On 10/19/2012 10:21 PM, Ted Mittelstaedt wrote:
there is no defined time it does it. Sometimes in the afternoon,
sometimes in the morning. This is under Perl 5.14.2. The core ram
consumed by the process does not appear to be increasing over time
that it is running.
Any suggestions?
IVe gon
Hi there,
This suggestion should be considered as a last chance.
I used monit in the past and had very nasty behaviors, multiple
instances of the same process running. May be monit is better know.
Debuging using your logs and knowledge is the first thing you should do.
Try to find what is your r
