Nigel Horne wrote:
> McDonald, Dan wrote:
>
>> how about:
>> Daily CVD 8721 (sigs: 32788, new: 1) at 04 Dec 2008 13-26 +
>
> Thank you for your suggestion. It's a great idea so we've made the
> change!
>
> -Nigel
And now you've sorted out twittering, how about fixing the
clamav-virusdb mai
On Wed, 2008-12-10 at 13:59 -0500, Nigel Horne wrote:
> McDonald, Dan wrote:
>
> > how about:
> > Daily CVD 8721 (sigs: 32788, new: 1) at 04 Dec 2008 13-26 +
>
> Thank you for your suggestion. It's a great idea so we've made the change!
I noticed. It looks good.
--
Daniel J McDonald, CCI
McDonald, Dan wrote:
> how about:
> Daily CVD 8721 (sigs: 32788, new: 1) at 04 Dec 2008 13-26 +
Thank you for your suggestion. It's a great idea so we've made the change!
-Nigel
--
Nigel Horne, [EMAIL PROTECTED]
Director of Product Management (ClamAV), Sourcefire,
http://www.sourcefire.co
> We'd like to hear any feedback people have who are following our
> Twitter channel at http://twitter.com/clamav.
Who is the intended audience? If an admin is not running freshclam out
of cron or equivalent scheduler, then they obviously don't care about
updates.
If they are running it out of cr
On Thu, Dec 04, 2008 at 11:52:56AM -0800, Kelson wrote:
>
> It doesn't take that long to set up an automatic process that will post
> without user intervention, or link an RSS feed to the account. It
> probably took them less time than it took me to write this email.
Sure, I'm just having a ran
I checked out the Twitter feed when it was announced. I didn't find it
useful, primarily because I don't feel the need to know when each update
hits. That's what I use freshclam for. As far as DB updates go, the
only notification I need is when freshclam fails, or when an unusually
long time
McDonald, Dan wrote:
> On Thu, 2008-12-04 at 12:45 -0500, Nigel Horne wrote:
>> Folks,
>>
>
> how about:
> Daily CVD 8721 (sigs: 32788, new: 1) at 04 Dec 2008 13-26 +
>
The proper phrasing is "on" and not "at"
James
signature.asc
Description: OpenPGP digital signature
___
Henrik K wrote:
> I can't help thinking that ClamAV staff might have something better to do
> than set up such things. Ok, atleast 76 people use it..
I agree... and posting daily CVD updates seems silly, given that the
information is available via DNS anyway.
"host -t txt current.cvd.clamav.net"
On Thu, Dec 04, 2008 at 12:45:51PM -0500, Nigel Horne wrote:
> Folks,
>
> We'd like to hear any feedback people have who are following our Twitter
> channel at http://twitter.com/clamav.
>
> If you're finding these updates useful please let us know. Also let us
> know if there is anything else
On Thu, 2008-12-04 at 12:45 -0500, Nigel Horne wrote:
> Folks,
>
> We'd like to hear any feedback people have who are following our Twitter
> channel at http://twitter.com/clamav.
the RSS feed from twitter truncates it much shorted, and you have a lot
of repeated characters, so it's not as usefu
Nigel Horne escribió:
> Folks,
>
> We'd like to hear any feedback people have who are following our Twitter
> channel at http://twitter.com/clamav.
>
> If you're finding these updates useful please let us know. Also let us
> know if there is anything else that you'd like us to put on that chann
--On 8 November 2008 15:00:36 + Nigel Horne <[EMAIL PROTECTED]> wrote:
> Folks,
>
> Notifications of ClamAV signature updates are now available via our
> Twitter feed at http://twitter.com/clamav. The notifications include
> information about
> the number of signatures added and the total nu
Nigel Horne wrote:
> Notifications of ClamAV signature updates are now available via our
> Twitter feed at http://twitter.com/clamav.
Just to add Sanesecurity updates are also available on Twitter, showing
all updates to the signatures, since July: http://twitter.com/sanesecurity
__
Quoting Dennis Peterson <[EMAIL PROTECTED]>:
> ANANT S ATHAVALE wrote:
>> Quoting Dennis Peterson <[EMAIL PROTECTED]>:
>>
>>> ANANT S ATHAVALE wrote:
Dear Developers,
When we run, clamscan, it gives output similar to the one below. Apart
from the information shown below, I woul
ANANT S ATHAVALE wrote:
> Quoting Dennis Peterson <[EMAIL PROTECTED]>:
>
>> ANANT S ATHAVALE wrote:
>>> Dear Developers,
>>>
>>> When we run, clamscan, it gives output similar to the one below. Apart
>>> from the information shown below, I would like to have one more filed
>>> that indicates the d
Quoting Dennis Peterson <[EMAIL PROTECTED]>:
> ANANT S ATHAVALE wrote:
>> Dear Developers,
>>
>> When we run, clamscan, it gives output similar to the one below. Apart
>> from the information shown below, I would like to have one more filed
>> that indicates the date/time of the last update of sig
Dear ANANT,
Are you using FreshClam to update your signatures? If so, you can check
the logs. You can write a shell script to call clamscan and have it do a
tail and grep on the FreshClam log.
Jim
Dear Developers,
When we run, clamscan, it gives output similar to the one below. Apart
from the i
Dear ANANT,
Are you using FreshClam to update your signatures? If so, you can check
the logs. You can write a shell script to call clamscan and have it do a
tail and grep on the FreshClam log.
Jim
Dear Developers,
When we run, clamscan, it gives output similar to the one below. Apart
from the i
ANANT S ATHAVALE wrote:
> Dear Developers,
>
> When we run, clamscan, it gives output similar to the one below. Apart
> from the information shown below, I would like to have one more filed
> that indicates the date/time of the last update of signature. What I
> mean is, it should be easy f
Dear Developers,
When we run, clamscan, it gives output similar to the one below. Apart
from the information shown below, I would like to have one more filed
that indicates the date/time of the last update of signature. What I
mean is, it should be easy for me to know, whether I have latest
20 matches
Mail list logo
