Way to control cfp.exe and cmdagent.exe

cfp.exe and/or cmdagent.exe can easily bring even a fairly powerful computer to its knees. I’d like to see the following added to CIS:

  1. A password-protected way to shut down and restart cfp.exe and/or cmdagent.exe if either or both crashes. At present, when cfp.exe locks up or becomes unresponsive for an extended period of time (not particularly unusual), the only way to restart it is to reboot the PC. (Actually, I’ve got a utility that can kill either or both processes, so I can restart it, but most users won’t have this ability.)

  2. User-configurable settings to place limits on resource usage for both cfp.exe and cmdagent.exe. (I’d like to be able to set a limit on the percent of CPU usage and disk access.)

As it stands, on a PC with an Intel Q9400 quad-core CPU, 4GB RAM, and a fast 1TB HDD, I’m seeing either or both cfp.exe and cmdagent.exe bring the system to a standstill for as long as 30 seconds at a time, even with real-time virus scanning disabled. During this time, CPU usage is high (IMO) but not extreme (25% to 40%), but responsiveness is at or near zero. IOW, it makes it seem like the system has crashed for what feels like a long time.

Mike

I second this motion!

THIS PROBLEM HAS BEEN REPEATED SINCE THE LAST TWO UPGRADES!!!

( I know I’m " shouting " )

I’d like to be able to recommend COMODO to my clients, but this situation turns back the clock to the bootup problems with Win95/98…go get a cuppa while the system comes up.

The other annoyance factor is the time and resources taken when the updater checks…usually another 5 minutes gone as a system gets hammered.

That " throttle " function could be easily added to the operations menu that requires admin privs anyway.

I’ve tried a workaround, but the basic problem remains…

on a 2 GHz laptop with 1.2 GB ram running XP Pro…5 minutes for bootup or a reboot clears the problem.