micah wrote:
> On Wed, 19 Sep 2007 18:37:13 +, micah wrote:
>
>> The logrotate.d/clamav does this:
>>
>> 1. Moves clamav.log to clamav.log.1
>> 2. runs: /etc/init.d/clamav-daemon reload-log, which is effectively a
>> kill -1 (ie. HUP).
>>
>> I've got the following associated config lines in cl
On Wed, 19 Sep 2007 18:37:13 +, micah wrote:
> The logrotate.d/clamav does this:
>
> 1. Moves clamav.log to clamav.log.1
> 2. runs: /etc/init.d/clamav-daemon reload-log, which is effectively a
> kill -1 (ie. HUP).
>
> I've got the following associated config lines in clamd.conf:
>
> LogSysl
On Wed, 19 Sep 2007 10:51:16 -0700, Dennis Peterson wrote:
> micah wrote:
>> I have a logrotate.d/clamav-daemon setup to rotate my clamav logs as
>> shown below:
>>
>>
>> Whereas before the logrotation the log contained a lot more clamav
>> information, including what viruses were caught.
>>
>>
micah wrote:
> I have a logrotate.d/clamav-daemon setup to rotate my clamav logs as
> shown below:
>
> Whereas before the logrotation the log contained a lot more clamav
> information, including what viruses were caught.
>
> Is there a better way to rotate the log?
>
Are you sending clamd a
I have a logrotate.d/clamav-daemon setup to rotate my clamav logs as
shown below:
/var/log/clamav/clamav.log {
rotate 5
daily
compress
delaycompress
create 640 clamav adm
postrotate
/etc/init.d/clamav-daemon reload-log > /dev/null
endscript
}
It succ
