Thanks, Nick.
 
It's a defensive mechanism I've used for years: keep the documentation with the settings.  I often do the same with registry keys by adding a text string and blathering away.  Adding dates and initials is also a good idea.
 
Andrew 8)
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Hayer
Sent: Tuesday, May 23, 2006 11:33 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Experience with 4.x

Very nice!

It looks like Matt has taught you well on how to comment a file   :)

-Nick

Colbeck, Andrew wrote:
I'd second that... on both the observed behaviour and the request for documentation.
 
I'm attaching my highly commented declude.cfg as a reasonable sample.
 
Andrew 8)
 
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt
Sent: Tuesday, May 23, 2006 10:36 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Experience with 4.x

David,

That did the trick.  I can't even see any messages in my proc folder any more.  I might suggest adding your explanation to the comments in the file just in case others feel the need to turn this on like I did.  I recalled the issues from the list and I turned it on because I didn't want the possibility of DNS crapping out and the leakage that this would cause.

Here's a screen cap of what my processor graph looks like now:



Thanks,

Matt



David Barker wrote:
The purpose of WINSOCKCLEANUP        ON is to reset the winsock, what
happens when using this setting is that when the \proc directory hit 0
decludeproc will finish processing all the messages in the \work before
checking the \proc again. As WINSOCKCLEANUP is to be used only by those who
experience DNS issues I would suggest running your tests again with
WINSOCKCLEANUP commented out and see how the behavior differs. Also having
the WAITFORMAIL to low can cause the CPU to process very high as it is
constantly checking the \proc I would suggest a minimum of 500-1000

David B
www.declude.com

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Matt
Sent: Monday, May 22, 2006 8:12 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Experience with 4.x

Darrell,

I put up two Windows Explorer windows side-by-side under normal volume 
and the pattern was consistent where the proc folder grows while the 
work folder shrinks until the work folder hits zero at which point the 
proc folder empties out and everything lands in work and then the 
pattern repeats with proc growing while work shrinks.

My settings are as follows:

THREADS        50
WAITFORMAIL    100
WAITFORTHREADS        10
WAITBETWEENTHREADS    50
WINSOCKCLEANUP        ON
AUTOREVIEW        ON
INVITEFIX    ON

Matt




Darrell ([EMAIL PROTECTED]) wrote:

  
It's a faulty design that leaves more than half a server's CPU 
capacity unused due to the mere fact that they wait for all threads 
to complete before moving in a new batch.
      
I can't speak to what you see on your server, but that is not how it 
is running on my server.  I just double checked again to make sure I 
am not crazy, but as I watch the thread count on my server 
(decludeproc) the threads fluctuate between 7 - 30 ( threads currently 
set to 50).  It is not uncommon to see the threads move as follow: 
11,8,10,7,15,....  While I was watching it I never seen a case where 
it went down low enough for the WAITFORMAIL setting to kick in.  
Watching the proc/work directory you can see files moving in and out, 
but never really emptying out.  Its possible what I am seeing is an 
anomaly or maybe I am interpreting it wrong.

Maybe David can comment on this.

Darrell
------------------------------------------------------------------------
invURIBL - Intelligent URI filtering plug-in for Declude, mxGuard, and 
ORF. Stop spam at the source the spamvertised domain.  More effective 
than traditional RBL's.  Try it today - http://www.invariantsystems.com
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.


    
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.


  

Reply via email to