On Tue, 2004-10-26 at 15:01, Jim Maul wrote: > Keep in mind while i agree the instructions are a little messed up for > the current versions of the software it uses, the instructions are the > way they are to correct problems and certain small errors that occured > in older versions of the sofware. Basically the instructions are > outdated in my opinion. I dont believe the reason for the > clamscan/clamdscan linking is still a valid reason as well as other > "workarounds" that were put in place. The instructions should be updated.
They were updated four days ago, and they are still grossly wrong. > > With that said, the person, yes, only 1 person, who created qmr is > obviously busy and this is not his full time job. I think it is great > that he has taken this amount of time out of his everyday life to > provide this great service for everyone....cut him some slack will ya? I believe the same problems have been in there for over a year. > Saying "for no reason other than ignorance and gross stupidity" is quite > incorrect and even downright rude. You don't think it's rude to break other peoples software, for which we then have to deal with the resulting mess, as witnessed by this thread? > You have NO idea why he set up the > instructions this way and you yourself are making huge assumptions. If > you have some constructive criticism here im sure it would be > appreciated but you previous comments were IMO not helpful at all. 1. Install ClamAV as per it's documentation, and then don't break it by linking clamdscan to clamscan. 2. If you want to use clamscan rather than clamdscan (for no reason, other then to send your CPU load to 100%, as per this thread), configure qmail-scanner to do so, it has a configure option for this). -trog
signature.asc
Description: This is a digitally signed message part
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
