On 2017-06-26 13:26, Carmel NY wrote:
On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated:
On 2017-06-25 18:16, Carmel NY wrote:
On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated:
From what I can see, the clamav-unofficial-sigs port works. It
determines if there are updates or
On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated:
>On 2017-06-25 18:16, Carmel NY wrote:
>> On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated:
>>
>>> From what I can see, the clamav-unofficial-sigs port works. It
>>> determines if there are updates or whether you have checked
On 2017-06-25 18:16, Carmel NY wrote:
On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated:
From what I can see, the clamav-unofficial-sigs port works. It
determines if there are updates or whether you have checked recently,
so that you do not inadvertently dos the signature servers. Wh
On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated:
>From what I can see, the clamav-unofficial-sigs port works. It
>determines if there are updates or whether you have checked recently,
>so that you do not inadvertently dos the signature servers. What is
>NOT working, apparently, is cla
> Am 25.06.2017 um 12:24 schrieb Carmel NY :
>
> I recently installed clamav-unofficial-sigs via the ports system. The
> port version is quite old,v5.3.2, while the current version is v5.6.2.
> In any case, I am receiving the following error message repeatedly:
>
> Jun 24 15:45:00 ERROR: clamsc
I recently installed clamav-unofficial-sigs via the ports system. The
port version is quite old,v5.3.2, while the current version is v5.6.2.
In any case, I am receiving the following error message repeatedly:
Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found
This is the full log fr
