Also for the record. We've experienced the banning - but only for RHEL4 hosts (which use up2date) and not RHEL5 (which use yum).
Our solution while we still have RHEL4 hosts and haven't implemented RedHat Satellite or Spacewalk was to push the runinterval out to 14400 for these hosts. This matches the 4 hour polling cycle that RedHat set with rhnsd. We disable rhnsd on these hosts too, so the only RHN polling mechanism is the puppet run. Iain On 4 November 2010 06:43, erikthered <[email protected]> wrote: > > > On Nov 3, 1:46 pm, Patrick Mohr <[email protected]> wrote: > > On Wed, Nov 3, 2010 at 10:37 AM, erikthered <[email protected]> > wrote: > > > I'm looking to get around a bit of a problem I've run into with > > > Puppet. On my puppet master, I have this definition: > > > > > Would that be the best way to handle this issue? Any opinions? > > > > I think they best way would be to put a caching proxy between your > computers > > and the mirror or run your own mirror. > > fair enough... > > just for the record it appears to be working while our local repo is > being built. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<puppet-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
