Protection database update concerns
The protection database updates are run from a scheduled task. The task is set to run every five minutes. It also has its error retry set to 10 retries at 30 second intervals.
The first issue is that during an error condition, the retries fill the five minutes between scheduled runs. In other words it will run every thirty seconds until it no longer has an error. But given that we've seen errors that do not resolve themselves, the task will run forever. When I saw this my Scheduler2 log was huge and growing.
Second issue: I have protection off and I also have the option to automatically check for updates turned off. But the scheduled update task is still running. I suppose this is for the purpose of telling us that there is an update.
With the Scheduler Manager,I have been able to easily set the five minute interval to something larger (e.g. 30 minutes) to keep the task from running so much. This has worked up to a point. What I found is that any time you go into the Protection Settings in the UI and hit OK, the tasks are rebuilt and the time goes back to 5 minutes again. And if you change the option to check for settings automatically, not only is the task changed but you get a new task number.
I believe the default check frequency should be something higher and there should be an option to modify it. My Avast anti virus checks every four hours.
I also think that if you are not updating automatically, the update task should not be run. A simple Check for Update button would be good. And if you've got protection completely turned off you should be able to live without the updates.
Ever wonder if updates may be tied to other checks such as application version updates? I suspect that they are. I also suspect that these tasks mentioned here are defaults hidden in the application executable files and are run by default when the executable runs.
Enchantech wrote:Ever wonder if updates may be tied to other checks such as application version updates? I suspect that they are. I also suspect that these tasks mentioned here are defaults hidden in the application executable files and are run by default when the executable runs.
I'm pretty sure these tasks are strictly related to the protection database updates. I'm not sure I understand what you mean by running when the executable runs. Are you talking about the UI? The rest of the app is always running. And looking at the Schedule2 logs, I can see that the tasks are running unrelated to the UI.
Bruno,
Check your email