Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Bugtraq
[Top] [All Lists]

Re: logwatch and logrotate might create a blind spot in reporting

Subject: Re: logwatch and logrotate might create a blind spot in reporting
Date: Wed, 26 Jan 2005 02:42:04 +0000 (UTC)
On Tue, 25 Jan 2005, Sami Pitko wrote:

There are some ways to make logwatch reports more reliable:

  * set "Archives = yes" in logwatch.conf. You might also want to tune
    archive settings in /etc/log.d/conf/logfiles/ to prevent unnecessary
    processing of really old archives. To cover the blind spot with range
    'yesterday' and weekly rotation, it is usually enough to specify for
    example "Archive = secure.1" in secure.conf

  * move logwatch and logrotate to happen at midnight

  * change date matching logic in /etc/log.d/scripts to match for example
    previous 24 hours

or add the following to the logrotate configuration file:

prerotate
  /full/path/logwatch
endscript


Then it will run logwatch just before it rotates the file.


<Prev in Thread] Current Thread [Next in Thread>