At 2:14 PM +0100 4/16/2010, Simon Hobson wrote:
I hope that by now you may be realising that many people quite
legitimately did not know anything until things broke this morning.
We did not have 6 months notice - our servers "just broke".
I'm sorry, did I miss something? This should be a non-event. A
viral scanner is a rather critical product therefore it should be
kept reasonably UP TO DATE. Version 0.95 was released in .... March
2009. Over a year ago! What have you been doing with your time over
the past year? Apparently you didn't bother to keep critical stuff
updated!? What else have you dropped the ball on?
At 3:28 PM +0100 4/16/2010, Simon Hobson wrote:
Bowie Bailey wrote:
Personally, I keep my servers updated, so the EOL issue didn't affect me,
And on another server (that's newer and is updated), I got bitten by
that as well when an update broke something and I had to manually
figure out which update was responsible and find versions of which
packages to roll back to (which had been deleted from the repos -
now I keep backup copies !)
So keeping up to date has it's own risks - hence why many people
take the attitude of "if it aint broke, don't fix it".
But being a YEAR out of date?
At 5:33 PM +0100 4/16/2010, Simon Hobson wrote:
please go fix it.
I will, now I know about it. But it would have been nice to do it at
a more convenient time, and with advance notice so I could use it to
get some resource allocated by management.
Wow. Freshclam has told you every day for .... a year+, that your
installation was out of date. Plus the 6 months of messages about
the EOL that have been posted. How much more notice do you need?
Of course, if you insist on keeping your system out-of-date, you
could just restore the database from your backup, and disable
freshclam. You do have backups, don't you?
- Dan.
--
- Psychoceramic Emeritus; South Jersey, USA, Earth.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
