On 4/21/10 8:03 PM, Steve Wray wrote:
I believe that best practice with this sort of thing is to only issue warnings and not to actually force a potentially harmful change without *express* consent of the user.
Suggest at least one way to inform all the users successfully that obsolete software is going to die soon - and don't let it slip past you in your solution that the ClamAV people have know way of knowing who they need to inform. And recall too, this: Filling their logs with warnings didn't work. Posting the notice on the front page of their website didn't work. Running commentary in this list didn't work. Announcing it in their Announcements list didn't work.
You don't know a way, they don't know a way, and I know for a fact it cannot be done, and the reasons why have been listed and the results show that despite adequate notification, some people failed to heed. They have to explain this inadequacy to management. It must have been a long day for them. I'm over it.
What the team did worked for me, but I pay attention - it's my job. And you know something? It really wasn't difficult. It takes me maybe 10 minutes to deal with a ClamAV upgrade and less time to discover one is necessary.
We're left with this: The "problem" affected only those that did not pay adequate attention. There is no cure for that.
So here's a message to everyone that was surprised: PAY ATTENTION because there's going to be a next time!
dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
