Dennis Peterson wrote:
>
> On 12/6/12 8:25 AM, franckm wrote:
>>
>>
>>
>>
>> Thanks it works now but I am not getting the log line when a new file is
>> getting scanned. I only get the result (OK line)
>>
>>
> Syslog uses a two-part record (facility.severity) to decide what to put
> into a log file. Assuming you are using the default LOCAL6 syslog
> facility you also need to set a severity level. Severity levels are
> inclusive of higher levels, so if your syslog.conf (or rsyslog.conf)
> entry is LOCAL6.warning you will not see lower lever log entries. Using
> LOCAL6.debug (equivalent to LOCAL6.*) in your syslog tool will show you
> everything ClamAV is capable of producing assuming you also have
> verbose logging enabled. Syslog-ng (rsyslog can as well) uses a very
> detailed rules scheme to produce the output and requires some study, but
> will also give you the full logging output.
>
> dp
> _______________________________________________
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://www.clamav.net/support/ml
>
>
Thanks Dennis.
Do you mean LogSyslog can provide more detailed log than LogFile?
Does the LogFacility setting apply to LogSyslog only or it also applies to
LogFile.
I have noticed my LogFacility setting does not have the default value. It is
set to LOG_MAIL not LOG_LOCAL6.
--
View this message in context:
http://old.nabble.com/clamav-no-timestamp-in-the-logs-tp34756576p34767324.html
Sent from the clamav-users mailing list archive at Nabble.com.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
