acorn_ikni

hah! literally as soon as i sent my previous post, the cpu usage dropped on it's own to 1%, much more acceptable! but i had been watching it for at least 20 minutes before that point. and very often when i run atop to examine which processes are consuming my resources, very often the esets_daemon is sitting very near the top of the list!

No updates going on... no scans, no activity at all, yet for some reason the background service is eating up far too many resources.... I have tried killing the daemon, but after it restarts, within a few minutes we're back to the same heavy resource consumption. Have sent you all the data i can think to gather, please let me know if there's any other debug info i can provide you (and instructions how to get to it!) Also, is there an 'official', or 'best' way to restart the daemon gracefully?? Thanks in advance for any assistance rendered :)