This bug was fixed in the package klamav - 0.45-0ubuntu1
---
klamav (0.45-0ubuntu1) jaunty; urgency=low
* New upstream release (LP: #213690, #258424)
- Upstream integration with clamav 0.94
- New icon set
* Drop 11-ukraine.patch and 12-clamav-0.94_build_fix.diff
- Inco
This will be fixed in KlamAV 0.45. Thanks!
--
scheduled scans do not run
https://bugs.launchpad.net/bugs/258424
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
I was able to find out some more information about the problem I am
having. I found that KlamAV modifies my crontab in order to run
scheduled scans:
crontab:
...
# KlamAV Scheduled Scan of /home/chris/
0 12 * * * /home/chris/.klamav/ScanWithKlamav_130808141030.sh
'/home/chris/'
# KlamAV Sch
Yes, klamav was running at those times. CPU usage did not increase and
no "Scanning..." icon appeared on the desktop, both of which I expected.
In addition, if I schedule a "once only" scan, when I return to the
scheduler the scheduled task is no longer present.
--
scheduled scans do not run
htt
I am able to do scheduled scans with the Hardy version. Klamav does
have to be running for the scan to work. Was klamav running when you
expected the scan to happen?
** Changed in: klamav (Ubuntu)
Status: New => Incomplete
--
scheduled scans do not run
https://bugs.launchpad.net/bugs/25
