Or this # clamscan -r / Dave, keep that smug attitude going. It only helps M$. Thank God I still have XP on another partition.
On Dec 23, 2007 5:12 PM, Dave M <[EMAIL PROTECTED]> wrote: > On Dec 23, 2007 7:07 PM, Baz <[EMAIL PROTECTED]> wrote: > > Dennis, > > > > Not apparently you're wrong. I spent at least two hours reading the > > wiki, support info from the website, various things from Google > > searches. Please note, that even you don't even know where it > > "should" be. This information should be readily apparent. Also, I > > didn't compile it, but installed pre-compiled packages from a > > non-official Debian repository. My main point is these Linux > > cheerleaders, who also whine about Microsoft's dominance, yet they > > can't even offer end-user-friendly applications so very basic to > > desktop security. > > > > Nevertheless, thank you for your input. > > > > Those darn linux cheerleaders. So how did you run your scan? You > should have been left with something like this: > > [EMAIL PROTECTED] ~]$ clamscan test/ > test/xpladv470.wmf: Exploit.WMF.A FOUND > test/lsd.exe: OK > test/wmf_exp.wmf: Exploit.WMF.A FOUND > test/lol.exe: OK > > ----------- SCAN SUMMARY ---------- > > Or did you use a GUI? > > > > On Dec 23, 2007 4:58 PM, Dennis Peterson <[EMAIL PROTECTED]> wrote: > > > Baz wrote: > > > > And where exactly is it? Do Linux developers intentionally make this > > > > shit difficult and still bitch about Windows/Norton's dominance? > > > > > > Please crush with all your being any desire to top post. > > > > > > Apparently you've not read anything yet so a good place to start is the > > > ClamAV Wiki. > > > The have a page especially for new users. > > > http://wiki.clamav.net/Main/WebHome#ClamAV_for_beginners > > > > > > I can't tell you where your log will be because I had nothing to do with > > > the > > > installation, but if you run the clamconf utility it will tell you where > > > it thinks > > > the log is. There are a number of user-defined choices about the log > > > which is why it > > > is unpredictable where it is. On my Sun systems it is in /var/log and I > > > use the > > > syslogd logger. Those were choices I made. > > > > > > The clamconf utility is often located in the same path as the clamdscan > > > and clamscan > > > executables, but that is also configurable. If you installed ClamAV from > > > source your > > > build process would tell you these things. If you installed from an RPM > > > then who ever > > > built your RPM has the info you need. > > > > > > I don't own, run, or use Linux so don't know what the developers do for > > > fun. > > > > > > > > > dp > > > _______________________________________________ > > > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > > > http://lurker.clamav.net/list/clamav-users.html > > > > > > > > > > > -- > > "...heart and soul....one will burn." > > - Joy Division > > _______________________________________________ > > > > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > > http://lurker.clamav.net/list/clamav-users.html > > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html > -- "...heart and soul....one will burn." - Joy Division _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
