ClearFoundation Tracker - ClearOS |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000854 | ClearOS | app-antivirus - Gateway Antivirus | public | 2012-11-28 04:02 | 2012-12-21 10:17 |
|
| Reporter | NickH | |
| Assigned To | user2 | |
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 6.3.0 Updates | |
| Target Version | 6.4.0 Beta 1 | Fixed in Version | 6.4.0 Beta 1 | |
|
| Summary | 0000854: Clamd log pollution |
| Description | With the default installation clamd logs to both /var/log/messages and /var/log/clamav/clamd.log.
This is because in /etc/clamd.conf both the parameter LogSyslog has been set to "yes" and LogFile has also been set pointing to /var/log/clamav/clamd.log. If either of these is unset then logging will only happen in a single log file. My preference is to log to /var/log/clamav/clamd.log only. |
| Steps To Reproduce | |
| Additional Information | In 5.2 LogFile was not set but LogSyslog was set to "yes". My preference is the other way round - and there is already a logrotate job which caters for this. |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2012-11-28 04:02 | NickH | New Issue | |
| 2012-11-28 10:17 | NickH | Note Added: 0000597 | |
| 2012-11-28 10:59 | user2 | Status | new => confirmed |
| 2012-12-14 11:34 | user2 | Note Added: 0000615 | |
| 2012-12-14 11:34 | user2 | Status | confirmed => resolved |
| 2012-12-14 11:34 | user2 | Fixed in Version | => 6.4.0 Beta 1 |
| 2012-12-14 11:34 | user2 | Resolution | open => fixed |
| 2012-12-14 11:34 | user2 | Assigned To | => user2 |
| 2012-12-14 11:34 | user2 | Target Version | => 6.4.0 Beta 1 |
| 2012-12-14 11:35 | user2 | Category | clamav => app-antivirus - Gateway Antivirus |
| 2012-12-21 10:17 | user2 | Status | resolved => closed |