I am using clamav on linux in the command line
When I use clamscan from the command line the log file does not show
timestamps
I have seen no option to turn timestamps on in log files
I'd like to get a timestamp especially for the "scanning" and "OK" log
lines.
I have seen that /etc/clamd.conf
On 12/6/12 3:05 AM, "franckm" wrote:
>
> I am using clamav on linux in the command line
>
> When I use clamscan from the command line the log file does not show
> timestamps
>
> I have seen no option to turn timestamps on in log files
>
> I'd like to get a timestamp especially for the "scanni
Al Varnell wrote:
>
> On 12/6/12 3:05 AM, "franckm" wrote:
>
>>
>> I am using clamav on linux in the command line
>>
>> When I use clamscan from the command line the log file does not show
>> timestamps
>>
>> I have seen no option to turn timestamps on in log files
>>
>> I'd like to get a
On 12/6/2012 7:28 AM, franckm wrote:
With clamdscan, it still does not show timestamps (see below)
The default config (/etc/clamd.conf) is to no show LogTimes. I have changed
that (LogTime yes). Is there anything I need to do after having changed the
clamd config?
Restart clamd.
releasemast
On Thu, Dec 6, 2012 at 10:04 AM, Bowie Bailey wrote:
> On 12/6/2012 7:28 AM, franckm wrote:
>
>> With clamdscan, it still does not show timestamps (see below)
>>
>> The default config (/etc/clamd.conf) is to no show LogTimes. I have
>> changed
>> that (LogTime yes). Is there anything I need to d
David Raynor wrote:
>
> On Thu, Dec 6, 2012 at 10:04 AM, Bowie Bailey
> wrote:
>
>
> Bowie is right. The logfile contents and the output on stdout are treated
> differently. Check your clamd.conf for the LogFile option (and make sure
> it
> is not commented out).
>
> Dave R.
>
> --
> ---
On 12/6/2012 10:43 AM, franckm wrote:
Ok I've done that. LogTimes are shown (in a weird datetime format) but the
file that I've just scanned is not listed at all:
clamdscan /tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt
/tmp/clamscan-franck-test/clamscan-franck-testclamscan-ma
Bowie Bailey wrote:
>
> On 12/6/2012 10:43 AM, franckm wrote:
>> Ok I've done that. LogTimes are shown (in a weird datetime format) but
>> the
>> file that I've just scanned is not listed at all:
>>
>>
>>> clamdscan /tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt
>> /tmp/clamscan
On 12/6/2012 11:25 AM, franckm wrote:
Bowie Bailey wrote:
On 12/6/2012 10:43 AM, franckm wrote:
Ok I've done that. LogTimes are shown (in a weird datetime format) but
the
file that I've just scanned is not listed at all:
clamdscan /tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.tx
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 sy
Bowie Bailey wrote:
>
> On 12/6/2012 11:25 AM, franckm wrote:
>> Bowie Bailey wrote:
>>> On 12/6/2012 10:43 AM, franckm wrote:
Ok I've done that. LogTimes are shown (in a weird datetime format) but
the
file that I've just scanned is not listed at all:
> clamdscan
>>
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
On 12/6/12 9:20 AM, franckm wrote:
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_MAI
On Thursday 06 December 2012 13:21:24 Bowie Bailey did opine:
> On 12/6/2012 11:25 AM, franckm wrote:
> > Bowie Bailey wrote:
> >> On 12/6/2012 10:43 AM, franckm wrote:
> >>> Ok I've done that. LogTimes are shown (in a weird datetime format)
> >>> but the
> >>>
> >>> file that I've just scanned i
On 12/6/12 10:44 AM, Gene Heskett wrote:
Speaking of clamd.conf, I wonder if some of you might be editing the wrong
clamd.conf file? I am not sure how it got to be, but according the the
launcher script in /etc/init.d. it is using /etc/clamav/clamd.conf, but I
have others also.
You should mak
On Thursday 06 December 2012 14:09:16 Dennis Peterson did opine:
> On 12/6/12 10:44 AM, Gene Heskett wrote:
> > Speaking of clamd.conf, I wonder if some of you might be editing the
> > wrong clamd.conf file? I am not sure how it got to be, but according
> > the the launcher script in /etc/init.d.
On 12/06/2012 12:12 PM, Gene Heskett wrote:
On Thursday 06 December 2012 14:09:16 Dennis Peterson did opine:
On 12/6/12 10:44 AM, Gene Heskett wrote:
Speaking of clamd.conf, I wonder if some of you might be editing the
wrong clamd.conf file? I am not sure how it got to be, but according
the t
On 12/7/12 11:44 PM, Jim Preston wrote:
On 12/06/2012 12:12 PM, Gene Heskett wrote:
On Thursday 06 December 2012 14:09:16 Dennis Peterson did opine:
On 12/6/12 10:44 AM, Gene Heskett wrote:
Speaking of clamd.conf, I wonder if some of you might be editing the
wrong clamd.conf file? I am not s
On Saturday 08 December 2012 07:34:39 Jim Preston did opine:
> On 12/06/2012 12:12 PM, Gene Heskett wrote:
> > On Thursday 06 December 2012 14:09:16 Dennis Peterson did opine:
> >> On 12/6/12 10:44 AM, Gene Heskett wrote:
> >>> Speaking of clamd.conf, I wonder if some of you might be editing the
>
On 12/08/2012 12:59 AM, Dennis Peterson wrote:
file. It can be anywhere but is specified by the configure/compile
operation, the installer if built from source, the RPM packager,
and the
command line in the launch script. Any or all can be screwed up or got
right by any of the people involved.
On 12/08/2012 05:43 AM, Gene Heskett wrote:
Yes, and one way is to do an uninstall before upgrading. I do this for
each of my clamav upgrades. I have found that each of the distro's tends
to customize the install location to their own liking and which is
usually not the same as anyone elses.
Jim
21 matches
Mail list logo
