[Logwatch] Suggestion/Request: feature for next version

NWCWEB Administration nwcwebadmin at nwcweb.com
Sun Apr 4 11:21:47 MST 2004

>-----Original Message-----
>From: logwatch-bounces at logwatch.org 
>[mailto:logwatch-bounces at logwatch.org] On Behalf Of ken
>Sent: Wednesday, March 03, 2004 8:26 AM
>Subject: [Logwatch] Suggestion/Request: feature for next version
>First, thanks for the effort in creating Logwatch.  I read 
>these reports every day in my email.  But when I do, I have no clue as to 
>how to check out what Logwatch is talking about.  To remedy this, I wish that
>Logwatch would output (in its mailout) the times, names of originating
>daemons, relevant config files, and other information about the reported
>events so that the reported activities would be easier to track down in
>the logs and elsewhere.
>Thanks again,


	What is it that you're missing clues on?  Most of what
Logwatch contains comes from standard locations, so depending
on the box you have and it's OS you should be able to dig up
those clues reasonably easy.

	You can turn on more verbose details in Logwatch from
what we've found, but I'd hate to have that level of detail
every day as it would use up more resources that already 

	Most of what we've seen in Logwatch points to key areas
that are easily remedied, such as intrusion attempts that need
to go into the Firewall (and you have to look those up in ARIN,
etc. to really get the proper answer as to blocking those attempts),
spam that needs to be blocked in spam filters, etc.  

	If you can provide more detail as to what sections are
confusing or lacking details, I might be able to pass on what
we've found and do to react to the reports.


      David J. Duffner
      VP Operations
      NWC Corporation
NWCWEB.com - Your Design & Hosting Solution!
Featuring Ensim Pro/Linux Servers, Hosted
Accounts, Web Design and e-Commerce services
NWC Corporation - Global e-Pay Solutions

More information about the Logwatch mailing list