Thanks for the time-line estimation. As I am new to Sanesecurity, I
didn't know what kind of time-line to expect.
The messages themselves I can ignore. I just like to keep everything up
to date and working properly as I can.
Scott
On 5/29/10 11:57 AM, Eric Shubert wrote:
No news. I expect
No news. I expect it might be a week or two before Bill gets the script
modified. It also might be that long before we can get a new QTP release
out as well. If you're annoyed by the emails, I suggest you remove the
job from cron.
Scott Hughes wrote:
Is there any news on this issue? I am stil
Is there any news on this issue? I am still getting the error message
emailed to me (looks like from a cron job) that says:
Clamscan reports Sanesecurity securiteinfo.hdb database integrity tested BAD -
SKIPPING
I get this email three or four times per day.
Thanks,
Scott
On 5/27/10 1:52
Hmmm. I wonder why I'm not seeing it, but it's not a big problem. Given
that a new script will be coming out in the near future, I'd just ignore
it for the time being, and see what things look like after installing
the new script w/ QTP when it's available.
--
-Eric 'shubes'
Scott Hughes wrot
Eric,
I received this message as an email to my postmaster account. I get it when
the cron job runs the command: /usr/sbin/clamav-unofficial-sigs.sh -c
/etc/clamav-unofficial-sigs.conf
Thanks,
Scott
On Thu, May 27, 2010 at 1:52 PM, Eric Shubert wrote:
> Scott Hughes wrote:
>
>> Many times
Scott Hughes wrote:
Many times I have noticed the following log entry:
Clamscan reports Sanesecurity securiteinfo.hdb database integrity tested BAD -
SKIPPING
In researching this, it appears that the Sanesecurity database is not
being updated. Is this the case or did I find incorrect inform
