Huge Dcc logdir

[Jeff A. Earickson]

Well, it seems to affect how dccifd gets launched too.  If I do:

% ps -ef | grep dcc
      dcc   755     1   0   Aug 04 ?           0:00 
/opt/dcc-1.3.40/libexec/dccifd -tCMN,NEVER, -Linfo,mail.notice 
-Lerror,mail.not
      dcc   756   755   0   Aug 04 ?           8:09 
/opt/dcc-1.3.40/libexec/dccifd -tCMN,NEVER, -Linfo,mail.notice 
-Lerror,mail.not

Note the "-t".  I don't specify the -t args anyplace explicitly.
It matches the manpage info I referred to.  Vernon Schryver referred
to the DCCM_LOG_AT setting of NEVER as a "primordial feature".
Back when DCC first crawled out of the swamp.  :)

Jeff Earickson
Colby College

On Wed, 9 Aug 2006, Dhawal Doshy wrote:

> Date: Wed, 09 Aug 2006 19:42:36 +0530
> From: Dhawal Doshy <dhawal at netmagicsolutions.com>
> Reply-To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> Subject: Re: Huge Dcc logdir
> 
> Jeff A. Earickson wrote:
>> I raised this issue a while back on the dcc mailing list (check the
>> archives).  If you don't want dcc logging, your choices are:
>> 
>> 1) Remove the log directory, and then live with the stat() complaints
>> from dccifd at start time in the syslog directory.
>> 
>> 2) Use the settings for the "-t" option.  See the manpage:
>> 
>> http://www.rhyolite.com/anti-spam/dcc/dccm.html#OPTION-t
>> 
>> The way to implement the "NEVER" feature for -t is to set:
>> 
>> DCCM_LOG_AT=NEVER
>
> Err.. isn't dccm the milter interface? and ideally should affect the daemon 
> (dccd)..
>
> - dhawal
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!