The line breaking should be fixed in 4.16.

>Also, while we're talking about the rebuild log, it would be nice to
>have a second counter for the other functions like generating tuplets
>and also maybe have an end date/time for each line where it says
>finished?  Something like Finished in 1647 second(s) [ 9/17/2009
>1:18:44 AM ]   That would help diagnose any server slowness during
>that time.

I'll add the time to each rebuildlog line like in maillog.txt.

>SMTP seems to stop responding for about a minute about 5 minutes and
>80 minutes into the rebuild for a minute or two.

Check the system workload ... the rebuild task does nothing to the 
MainThread (SMTP) - but it could take 100% of one CPU-core. You can 
increase the 'RebuildThreadCycleTime' - this will possibly prevent the 
rebuildthread from using 100% CPU, but it will increase the run time of 
the rebuild task!

It's on you to design your system - keep in mind, that this is a 
multithreaded version. Having ASSP (+OCR plugin?),ClamAV and MTA on a high 
loaded system with less than 4 cores - will make trubble. 


Thomas




K Post <nntp.p...@gmail.com> 
18.09.2009 16:22
Bitte antworten an
ASSP development mailing list <assp-test@lists.sourceforge.net>


An
ASSP development mailing list <assp-test@lists.sourceforge.net>
Kopie

Thema
Re: [Assp-test] Antwort: Re: Antwort: Rebuild log - HELO line






Just realized that the lines I was looking at were from spamdb, not
spamdb.helo (still could use fixing though).

The spamdb.helo error is more interesting.

In my EMAIL, I get on ONE line:

Resulting file c:/assp/spamdb.rb.tmp' is 6,223,877 bytes Bayesian
Pairs: new - 261,401 : altogether - 315,643 cleaning old Spamdb.helo
records done - cleaning old Spamdb.helo records

but in the text log, the returns show.

Resulting file c:/assp/spamdb.rb.tmp' is 6,223,877 bytes
Bayesian Pairs: new - 261,401 : altogether - 315,643
cleaning old Spamdb.helo records
done - cleaning old Spamdb.helo records

With the spamdb logging (not spamdb.helo, but spamdb), in the email
the log lines are on 1 line, but in the text file, there's a line
break before the "done - cleaning old spam db records line" and one
before the "done" ("for generating weighted bayesian tuplets...".

I didn't spot the difference in the code.

\n should work.  I use that with win32 all of the time.  no need for
\n\r unless I'm missing something.


Also, while we're talking about the rebuild log, it would be nice to
have a second counter for the other functions like generating tuplets
and also maybe have an end date/time for each line where it says
finished?  Something like Finished in 1647 second(s) [ 9/17/2009
1:18:44 AM ]   That would help diagnose any server slowness during
that time.

SMTP seems to stop responding for about a minute about 5 minutes and
80 minutes into the rebuild for a minute or two.


On Fri, Sep 18, 2009 at 10:03 AM, K Post <nntp.p...@gmail.com> wrote:
> Interestesting thing about the scalar function.  At least I can
> finally put a tick mark in the "I'm not crazy" column.
>
> As for the carriage returns.  I looked at the code and compared to my 
text log.
>
> (v15)
> 1) line 37111 has the return before the "Generating weighted Baesian
> tuplets...." line
> 2) line 37149 has the return AFTER the "cleaning old spamdb records" 
line
> 3) line 37162 also has the retturn after cleaning old spamdc records
> 4) line 37165 just has "done"
>
> SO, In my log, I get:
> Generating weighted Bayesian tuplets...cleaning old Spamdb records
> done - cleaning old Spamdb records
> done
>
> I think you need to to change #2 and 3 to have the before the line.
>
> Also, I'd change line #4 from just "done" to "done - Generating
> weighted Bayestian tuplets"
>
> To say that "you do what you can" is definitely an understatement.
>
>
> On Fri, Sep 18, 2009 at 3:12 AM, Thomas Eckardt/eck
> <thomas.ecka...@thockar.com> wrote:
>> $count = scalar(%main::SpamdbHelo);
>>
>> If've learned something new - scalar(%main::SpamdbHelo) results in a
>> xxx/yyy string  (http://www.perlmonks.org/?node_id=173677
>> ).
>>
>> This will be fixed in 4.16 (sorry).
>>
>>>I think there should be a carriage return before "cleaning old
>> Spamdb.helo"
>>  look in to the code - there are "\n" at the end of every logline :
>>
>>    &rb_printlog("Bayesian Pairs: new - " . &rb_commify($pairs) . " :
>> altogether - " . &rb_commify($allpairs) . "\n");
>>
>> This is unix style (without "\r").
>>
>>>(I LOVE the menu options at the top - great idea me!  Execllent
>> implementation Thomas!)
>>
>> I do what I can.
>>
>> Thomas
>>
>>
>>
>>
>>
>>
>>
>> K Post <nntp.p...@gmail.com>
>> 18.09.2009 04:56
>> Bitte antworten an
>> ASSP development mailing list <assp-test@lists.sourceforge.net>
>>
>>
>> An
>> ASSP development mailing list <assp-test@lists.sourceforge.net>
>> Kopie
>>
>> Thema
>> Re: [Assp-test] Antwort: Rebuild log - HELO line
>>
>>
>>
>>
>>
>>
>> I'm running 0.4.15 now.  I haven't modified the code at all.  I've
>> removed rebuildspamdb.pl just to be safe, but has never run on this
>> machine.
>>
>> I just ran the rebuild and in the log I >>still<< get:
>>
>> HELO Blacklist: new -1652 : altogether - 1122/2048 HELOs
>> (with the number slash number).
>>
>> I looked at the code (did a case sensitive search for HELOs) and found
>> line 37225:
>> &rb_printlog( "\nHELO Blacklist: new -" . scalar(@Helo) . " :
>> altogether - ". $count . " HELOs\n" );
>>
>> The line before has $count being set:
>> $count = scalar(%main::SpamdbHelo);
>>
>> Any idea how this could be set to number/number and what this could 
mean?
>>
>> Also, note that in the rebuild log I see a line like this:
>>
>> Resulting file c:/assp/spamdb.rb.tmp' is 6,223,877 bytes Bayesian
>> Pairs: new - 261,401 : altogether - 315,643 cleaning old Spamdb.helo
>> records done - cleaning old Spamdb.helo records
>>
>> I think there should be a carriage return before "cleaning old
>> Spamdb.helo"
>>
>> (I LOVE the menu options at the top - great idea me!  Execllent
>> implementation Thomas!)
>>
>>
>>
>> Thanks all.
>>
>>
>> On Thu, Sep 17, 2009 at 10:45 AM, Fritz Borgstedt <f...@iworld.de> wrote:
>>>
>>> ASSP development mailing list <assp-test@lists.sourceforge.net>
>>> schreibt:
>>> >I may have copied it, along with config files, from a 1.4x
>>> >installation.
>>> >However, it shouldn't be running as I definitely didn't schedule it.
>>>
>>>
>>> It is NOT a text from rebuildspamdb.pl V1.
>>>
>>>
>>>
>> 
------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart 
your
>>> developing skills, take BlackBerry mobile applications to market and
>> stay
>>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>> now&#33;
>>> http://p.sf.net/sfu/devconf
>>> _______________________________________________
>>> Assp-test mailing list
>>> Assp-test@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>> 
------------------------------------------------------------------------------
>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart 
your
>> developing skills, take BlackBerry mobile applications to market and 
stay
>> ahead of the curve. Join us from November 9&#45;12, 2009. Register
>> now&#33;
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>>
>>
>>
>> DISCLAIMER:
>> *******************************************************
>> This email and any files transmitted with it may be confidential, 
legally
>> privileged and protected in law and are intended solely for the use of 
the
>>
>> individual to whom it is addressed.
>> This email was multiple times scanned for viruses. There should be no
>> known virus in this email!
>> *******************************************************
>>
>> 
------------------------------------------------------------------------------
>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart 
your
>> developing skills, take BlackBerry mobile applications to market and 
stay
>> ahead of the curve. Join us from November 9&#45;12, 2009. Register 
now&#33;
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Assp-test mailing list
>> Assp-test@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>>
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register 
now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to