Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
For all I know it should only run when your machine is idle.
It sure has lot's of actions which NIS is performing when idle but please keep in mind they all are actions to keep your machine more safe
I understand that NIS runs stuff when my machine is idle. I don't have a problem with that. I do have a problem with it running stuff when my machine is not idle. I could understand running things like automatic update when the machine is not idle, if it has not run in a few days.
I can't think of any instance where idle quick scan or norton community watch should run when the system is not idle. That is what I'm complaining about.
Morac,
The tasks you list will make their best effort to run during idle. If an idle time is not encountered, then they will be forced to run after a reasonable timeout. This timeout varies from task to task.
Since you are taking the computer out of the running state when you are done using it, NIS never has an oppertunity to run idle processing.
The Pulse Updates are not designed to run during an idle period, as this task only takes about a second to complete.
The rest of the tasks you list will wait between six hours and five days for an idle period, and then will be forced to run without any further delay. This timeout varies between the individual background tasks, and is a safeguard to ensure your computer is always protected against the latest threats.
Note that many of the much more resource intensive background tasks will always wait for idle.
If at any point you notice NIS has begun this critical background processing while you're not idle and you determine you need it to stop, you can defer this processing by enabling "Silent Mode". This option is available by right-clicking the tray icon and selecting "Turn On Silent Mode".
Regards,
Mike
MikeO,
The thing is that I only took my machine "out of the running state" for about 24 hours. This is no where near the 5 day limit you mention. Normally when I resume it I'll work for a bit and then let it idle. I've found though that it seems to kick off most background jobs (many all at the same time) almost immediately when I come out of hibernation.
Like I said I could understand automatic live updates wanting to run if it's been more than 24 hours, though realistically it should try and wait for an idle time shortly after resuming from hibernation. I have no idea why Norton Community Watch (which can sometimes take nearly 5 minutes) feels the urgent need to run almost immediately after resuming from hibernation and usually at the same exact time that Automatic Live Updates do.
It would be nice if NIS 2009 worked like NIS 2008 for the purpose of resuming from stand by or hibernation. NIS 2008 would not trigger live update until 15 minutes after coming out of any power down mode (off, stand-by or hibernation). NIS 2009 wait time appears to be much shorter and NIS 2009 and Google Desktop (another program that runs periodically) normally end up getting into a fight as to who wants to run first after resuming from hibernation.
Moved post to new thread, as it is a different issue.