On Fri, Apr 16, 2010 at 5:24 PM, Jim Preston <jimli...@commspeed.net> wrote:
> > On Apr 16, 2010, at 1:07 PM, Aecio F. Neto wrote: > > On Fri, Apr 16, 2010 at 4:27 PM, Eric Rostetter >> <rostet...@mail.utexas.edu>wrote: >> >> Quoting Gary MacKay <g...@edisoninfo.com>: >>> >>> No one. Only very old installs, not all installs. >>> >>>> >>>>> So who made who god to decide which servers get shutdown? >>>>> >>>> >>>> >>> No servers were shutdown. And the creators of the software and providers >>> of the updates (same people) decided, which is their right as the >>> creators >>> of the software and the providers of the updates. If you don't like it, >>> then don't use their updates and/or software. Your choice. >>> >> >> >> This is semantics, servers/services were stopped and this is no good no >> matter what. >> There are tons of other situations that spread out virus too and clamav >> team >> cannot avoid them all too. >> Causing interruption of a service one does not manage and is not >> responsible >> for is totally intrusive to say the less. >> >> I just hope all this noise contributes to such situation never to happen >> again in any software I use or manage. >> >> If one can consider this as normal just because it was announced to >> happen, >> I should subscribe to the kernel list immediately. Should I? >> LOL >> > > No, servers / services stopped because that is what the SA (or whoever you > want to blame for setting up the system) CHOSE to have happen! If you want > mail to be delivered when clamd fails, configure your system to do so I > personally prefer to have my mail stopped rather than irresponsibly sending > mail. If spam / infected mail were not a problem, then open relay mail > systems would be the norm and not blacklisted..... Alas, we do not live in a > perfect world :^( > So, if you feel that the "Mail must go through", configure your system to > do so and stop whining that you failed to have your system configured to do > what YOU wanted it to do. > clamd is a service and it was stopped. Anyway, I do not agree with the approach that was used. No external entity has the right to interfere with behavior of a system. When that happens, normally, it is called invasion or cracking or you name it. I manage some web filtering proxies that uses clamd. When clamd fails it fails. And yes, because I chose it to. Fortunately, I had upgraded all my installs before April, 15 and I was *not* affected. I am just putting my voice against a practice that I do not agree. Similar to this: I do not want kernel to should itself after some time because it identified to have a bug or so. I do not want my SQL server to shutdown itself to prevent something. Etc. This is all I had to say about that. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
