Bug 63380

Summary:	rhn-applet needs a tunable for how often it checks
Product:	[Retired] Red Hat Linux	Reporter:	Bill Nottingham <notting>
Component:	rhn-applet	Assignee:	Robin Norwood <robin.norwood>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-07 14:33:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill Nottingham 2002-04-13 05:01:44 UTC

Currently, it appears to be checking every 30 seconds... this seems to me to be
way too often. It would be nice if:

a) the default was longer
b) it was tunable

Comment 1 Chip Turner 2002-04-14 03:45:32 UTC

there are different things going on.  the applet polls the model evern 10
seconds now (though it no longer changes the icon).  this poll is almost always
a noop though -- it chgecks mtime on /var/lib/rpm/Packages, then checks to see
if it's time to do RPC again.  the time for next RPC is actually sent down from
our servers in RWC, specifically not a user tunable parameter, so that we can
better control load.

none of those numbers really should be user-tunable though.

Comment 2 Gene Czarcinski 2002-08-10 19:34:08 UTC

Right now it appears to consume a fair amout of CPU cycles doing this checking.

Also, much of the time it is displaying a "?" on grey instead of a "check" on
blue or "!" on red.

When I click the "?", a popup message says "Network Error - 12: SSL_connect error"

The CPU cycles really need to be cut!

Comment 3 Robin Norwood 2005-10-07 14:33:11 UTC

Closing this bug.  The original issue is wontfix as described in comment #1, and
newer versions of the applet are better about cpu resources.  (Memory usage is
another matter - see bug #170022.)