KeepUp2Date - High cpu usage?

hottcarl · 02-05-2009, 06:27 AM

Keepup2date is causing high cpu usage every so often - this is used by the virus blocker, correct? If so, why is it still running even though I removed both of the virus blockers from the rack?

far182 · 02-06-2009, 08:44 AM

I am also seeing this problem. It can put the CPU to 1+ load on high performance systems. I see this happen several times a day.

dmorris · 02-06-2009, 09:11 AM

I agree keepup2date is kinda a CPU intensive - its the kaspersky signature updater.

you can remove the cron job from /etc/cron.hourly/ if you want but then it won't be getting hourly updates obviously...

far182 · 02-06-2009, 10:19 AM

I am no Linux guru, but isn't there a way to run this on an extremely with an extremely low priority so that it won't take many CPU %?

hottcarl · 02-06-2009, 12:24 PM

Alright, that script has been disabled. Any idea why this would still run even if Kaspersky isn't running though?

dmorris · 02-06-2009, 01:15 PM

Quote:

Originally Posted by hottcarl

Alright, that script has been disabled. Any idea why this would still run even if Kaspersky isn't running though?

because the daemon is still active.

neiby · 07-15-2009, 11:26 AM

I just noticed that keepup2date is adding a lot of load to our machine, too. We had been averaging around a load of 1 or so, but this daemon pushes it to >3.5 while it's updating and it seems to take a long time.

Is there a way to make this a lower priority? And would it be possible to add a feature in the UI that lets us change the update frequency? Once a day is plenty for us.

ITDude69 · 09-19-2009, 09:37 AM

You could just move the "kav-cron" job file from the /etc/cron.hourly to the /etc/cron.daily dir if you only need it to run once a day.

hitman · 09-19-2009, 05:54 PM

I noticed the same issue awhile back and I did what ITDude69 suggested and moved the kav-cron job and everything seems to be working great now. Have the job run in the middle of the night when the load will not be noticed.

u3b3rg33k · 09-19-2009, 09:34 PM

If you nice the crap out of it it'll get out of the way when something important wants to happen. It'll still take whatever it can get provided it's not in the way, so you won't see lower cpu load, it just won't be an issue (assuming it is an issue...).

02-05-2009, 06:27 AM	#1 (permalink)
hottcarl Untangler Join Date: Sep 2008 Posts: 44	KeepUp2Date - High cpu usage? Keepup2date is causing high cpu usage every so often - this is used by the virus blocker, correct? If so, why is it still running even though I removed both of the virus blockers from the rack?

02-06-2009, 09:11 AM	#3 (permalink)
dmorris Untangle Junkie Join Date: Nov 2006 Location: San Mateo, CA URLs submitted: 10 Posts: 10,614	I agree keepup2date is kinda a CPU intensive - its the kaspersky signature updater. you can remove the cron job from /etc/cron.hourly/ if you want but then it won't be getting hourly updates obviously... __________________ Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself. If you need Untangle support please call or email support@untangle.com

07-15-2009, 11:26 AM	#7 (permalink)
neiby Master Untangler Join Date: Jun 2009 Location: Denver, CO Posts: 603	I just noticed that keepup2date is adding a lot of load to our machine, too. We had been averaging around a load of 1 or so, but this daemon pushes it to >3.5 while it's updating and it seems to take a long time. Is there a way to make this a lower priority? And would it be possible to add a feature in the UI that lets us change the update frequency? Once a day is plenty for us. __________________ Disclaimer: I may or may not have had enough coffee when I'm posting. Interpret my responses thusly.

09-19-2009, 05:54 PM	#9 (permalink)
hitman Untangler Join Date: Oct 2008 Location: Cincinnati OH Posts: 66	I noticed the same issue awhile back and I did what ITDude69 suggested and moved the kav-cron job and everything seems to be working great now. Have the job run in the middle of the night when the load will not be noticed. __________________ Karl Hart www.cyberconsecurity.com

Protect

Filter

Perform

Connect

Manage

Add-Ons

02-06-2009, 08:44 AM	#2 (permalink)
far182 Master Untangler Join Date: Aug 2008 URLs submitted: 1 Posts: 946	I am also seeing this problem. It can put the CPU to 1+ load on high performance systems. I see this happen several times a day.

02-06-2009, 10:19 AM	#4 (permalink)
far182 Master Untangler Join Date: Aug 2008 URLs submitted: 1 Posts: 946	I am no Linux guru, but isn't there a way to run this on an extremely with an extremely low priority so that it won't take many CPU %?

02-06-2009, 12:24 PM	#5 (permalink)
hottcarl Untangler Join Date: Sep 2008 Posts: 44	Alright, that script has been disabled. Any idea why this would still run even if Kaspersky isn't running though?

09-19-2009, 09:37 AM	#8 (permalink)
ITDude69 Newbie Join Date: Sep 2009 Posts: 1	You could just move the "kav-cron" job file from the /etc/cron.hourly to the /etc/cron.daily dir if you only need it to run once a day.

09-19-2009, 09:34 PM	#10 (permalink)
u3b3rg33k Master Untangler Join Date: Nov 2008 Posts: 228	If you nice the crap out of it it'll get out of the way when something important wants to happen. It'll still take whatever it can get provided it's not in the way, so you won't see lower cpu load, it just won't be an issue (assuming it is an issue...).