> > Red Hat support has come back and said that 60 minutes is considered > an > > abusive rate and have suggested that 240 minutes is the acceptable > minimum. > > This clearly seems to conflict with their documentation. > > > > Are any of you using rhnsd and aware of this policy? If you use > rhnsd for > > periodic check-in and patch management through RHN, what value do you > use? > > Patch management tools like puppet or cfengine can often cause this > without the reasons being entirely obvious. Are you using any of those > sort of tools in conjunction with RHN?
The case got passed along to the RHN team who I think may have suggested a workable theory. The rhnsd daemon 60 minute check-in rate is fine but in my case the other culprit seems to be not puppet or cfengine but rather yum-updatesd with its default check-in interval of 10 minutes. The tech said that the actual rate is not the problem but, rather, a system exceeding a certain number of check-ins in a 24 hour period is what triggers the lock-out. Matt _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
