User Activity

  • Posted a comment on discussion Help on Logwatch

    I think getting a copy of the entire repository with the git clone command is the best option. It allows you to keep up to date with the code. [There should be 'RO' button on the page I previously described. It executes the following: git clone git://git.code.sf.net/p/logwatch/git logwatch-git, where logwatch-git is the name of the directory. The problem with doing an individual service is that you need to know which scripts and configuration files need changing. Among the Logwatch files there is...

  • Posted a comment on discussion Help on Logwatch

    The current http-error script and configuration files in the git repository use the new date format you listed, and should also detect the [ssl:warn] statements. You can download it from sourceforge.net, under the git tab in the Logwatch project page: https://sourceforge.net/p/logwatch/git/ It gives different options for downloading, including git clone and downloading a zip file.

  • Posted a comment on discussion Help on Logwatch

    You may have an old version of Logwatch. The http-error script was updated for Apache 2.4 some time ago. There is no apache2 service in the default Logwatch. You might be looking for the http service. As for php, that service script has not been updated in a long time, and needs work.

  • Committed [e8eb23]

    [exim] Ignore office 365 connector disconnects, by Josh Soref

  • Committed [dcb795]

    [secure] counting systemd-logind new logins; patch by Christian Mertes

  • Committed [f6b3e9]

    [logwatch.pl] fixed base64 encoding; patch by Jan Synacek

  • Committed [c11790]

    [cron] Counting more SELinux context errors; patch by Christian Mertes

  • Committed [28776d]

    [logwatch.pl] added support for xzcat, by Stefan May

View All

Personal Data

Username:
bjorn1
Joined:
2010-03-29 19:57:01

Projects

  • Project Logo Logwatch   Last Updated:

Skills

  • No skills entered.

Personal Tools