Bug 720089 - would like a way to test an error
Summary: would like a way to test an error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: clamav
Version: 14
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-09 05:58 UTC by Paul
Modified: 2012-01-26 04:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-26 04:06:19 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Paul 2011-07-09 05:58:04 UTC 
Description of problem:
While installing and working with clamav, it sure would be nice if there were an option to clamscan that would allow me to simulate an error so I could see what happens when I have it being driven by rc.local and cron.d

Version-Release number of selected component (if applicable):


How reproducible:
N/A

Steps to Reproduce:
1. N/A
2.
3.
  
Actual results:
N/A

Expected results:
N/A

Additional info:
This is really a "sug" rather than a "bug", but I don't see anything that allows me to flag such

Thanks in advance,
Paul
Comment 1 Paul 2011-10-18 06:47:33 UTC 
I just found eicar.com on the web and this satisfies my "sug". That being said, your documentation should mention such as a way to "test ClamAV"

I would normally close this sug but I think I would like to keep it open in the hopes of getting a response to confirm 1) eicar.com is a valid test in the ClamAV developer's opinion and 2) a comment about whether putting this link/info on your website is a good idea (and if not, why)

Thanks,
Paul
Comment 2 Paul 2012-01-26 04:06:19 UTC 
After bring up a system on F16 Ffce, submitting various bugs (including some on clamav), and now doing a documentation clean-up, I can see this is still open and the eicar.com site worked great for my installation / testing.

I'm closing this bug as it is not needed
Note You need to log in before you can comment on or make changes to this bug.