How to restart On Access Scanner

---

ZRL1 wrote:

Reading through the various posts in this thread, I have to wonder if the problem is at least partially tied to the computer being constantly "on" in some form. I've simply never seen the On Access Scanning issue happen on either my Mac Pro 5,1 or a rMBP 2013. In both instances the computers are either running or shut down. They never sleep, since, when booting from an SSD the wait is very short, and I believe the sleeping process involves writing RAM contents to permanent storage which, with a HD is irrelevant but with an SSD is eating into its usable life. I've also seen on the Apple Communities that seemingly obscure problems that people have are sometimes solved by simply rebooting, which is a lot less common than I would have thought. I also wonder if the transition-to-sleep-mode process may be a bit less orderly than a clean shut-down, especially for third party software that's busy doing something when that happens. On occasion I've seen something I'm doing slow down as Sophos starts its periodic update, especially to a whole new version. That's why part of my startup process is to force Sophos to "Update Now" so it's done before I get busy.

That's not to say that constantly running software shouldn't be immune to being run non-stop, but with so many other things going under the hood, sometimes simply shutting down in orderly fashion can be a good thing.

---

I would think that any software which has processes sensitive to disruption due to the system transitioning to low-power or sleep mode would be designed to take the possibility into accout and have some means of preperly recovering those processes that were interupted. At least, to my thinking that would be intelligent design. That being said, I do recognize that far too many -- perhaps not the majority, but still too many -- programmers and software designers operate in a fantasy world where every user only does things the way those software designers demand and any user who does anything differently than those software designers demand get what they deserve when the application misbehaves. Sorta like a car designer telling a driver that if the car misbehaves when the make a left turn it's obviously the drivers fault because, after all, the car was designed only to make right turns and don't expect them to "fix" the problem because there isn't a problem: drivers simply have to stop insisting on making left turns -- THAT'S the problem!!

---

ZRL1 wrote:

Reading through the various posts in this thread, I have to wonder if the problem is at least partially tied to the computer being constantly "on" in some form. I've simply never seen the On Access Scanning issue happen on either my Mac Pro 5,1 or a rMBP 2013. In both instances the computers are either running or shut down. They never sleep, since, when booting from an SSD the wait is very short, and I believe the sleeping process involves writing RAM contents to permanent storage which, with a HD is irrelevant but with an SSD is eating into its usable life. I've also seen on the Apple Communities that seemingly obscure problems that people have are sometimes solved by simply rebooting, which is a lot less common than I would have thought. I also wonder if the transition-to-sleep-mode process may be a bit less orderly than a clean shut-down, especially for third party software that's busy doing something when that happens. On occasion I've seen something I'm doing slow down as Sophos starts its periodic update, especially to a whole new version. That's why part of my startup process is to force Sophos to "Update Now" so it's done before I get busy.

That's not to say that constantly running software shouldn't be immune to being run non-stop, but with so many other things going under the hood, sometimes simply shutting down in orderly fashion can be a good thing.

---

I would think that any software which has processes sensitive to disruption due to the system transitioning to low-power or sleep mode would be designed to take the possibility into accout and have some means of preperly recovering those processes that were interupted. At least, to my thinking that would be intelligent design. That being said, I do recognize that far too many -- perhaps not the majority, but still too many -- programmers and software designers operate in a fantasy world where every user only does things the way those software designers demand and any user who does anything differently than those software designers demand get what they deserve when the application misbehaves. Sorta like a car designer telling a driver that if the car misbehaves when the make a left turn it's obviously the drivers fault because, after all, the car was designed only to make right turns and don't expect them to "fix" the problem because there isn't a problem: drivers simply have to stop insisting on making left turns -- THAT'S the problem!!