Re: Dovecot

Tom Metro wrote:
> I currently have the filter installed as 
> /etc/logwatch/scripts/shared/dovecottostd. It seems a little odd to put 
> a service-specific filter in shared, but given that it is needed to 
> pre-process the log lines before they're seen by the service filter, I'm 
> not sure where else it would go.

I forgot about the scripts/logfiles/ directory, however it isn't 
entirely clear how it works.

http://www2.logwatch.org:81/tabs/docs/HOWTO-Customize-LogWatch.html

   B. Executable Structure
   ...
   logfiles:	This subdirectory may contain subdirectories with
		logfile group names.  The executables under each of
		these subdirectories are automatically invoked when
		running	a service that uses the corresponding
		logfile group name.

In what order are they invoked relative to each other and relative to 
the filters named in the log file group conf file?

I had in logfiles/dovecot.conf:

*DovecotToStd
*ApplyStdDate

Then I moved my scripts/shared/dovecottostd to 
scripts/logfiles/dovecot/dovecottostd and commented out *DovecotToStd 
and things failed to work.

I went back and commented out both filter lines in the conf file, 
renamed dovecottostd to 01dovecottostd, and created a symlink in that 
same directory from 02applystddate -> 
/usr/share/logwatch/scripts/shared/applystddate*.

Then it worked again.

So apparently it runs the scrips in scripts/logfiles/ in alpha-sort 
order, and runs them after filters named in the conf file. The 
documentation should reflect this.

Also, doesn't this mechanism limit the ability to override filters in a 
local configuration? If, for example, I didn't want cron's 
scripts/logfiles/cron/applydate to run on my system, short of creating a 
local scripts/logfiles/cron/applydate that does a no-op, can you 
override it?

  -Tom

-- 
Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/