Re: redhat network

Rather than using a common multiple like 15 minutes, I have been succesful
in using a 'prime' number of minutes. Like 13, 17, 19, etc. Reason being,
Most schedules hit on even intervals. By using a 'prime' number, you may
miss the regularly scheduled load by just enough to get in... Although this
is a drag to do in some schedulers... But for extended attempts as
mentioned, Can be the difference in getting in.

And not that I am advocating the barrage method of getting things done, but
not only does this help a single person get in, but also helps even out the
surges for everyone else too.


----- Original Message -----
From: "Michael Schwendt" <[email protected]>
To: <[email protected]>
Sent: Saturday, September 21, 2002 12:13 PM
Subject: Re: redhat network


> On Sat, 21 Sep 2002 17:40:22 +0200, Johan Hendriks wrote:
>
> > Yes today there is maintenence but not the whole week before i guess
> > I did not succeed to update my new system the whole week.
> >
> > I even put up2date in a cron job checking every 15 minutes but the
> > whole week no go.
>
> Ouch! That is part of the problem with Red Hat's free basic
> entitlements for RHN. If many more users run up2date "every 15
> minutes", RHN will be terribly busy all the time.
>
> Apart from that, there is no point in running up2date so often,
> because heavy load at RHN would kick a "free user" out of the
> service any time even if you managed to connect and start
> downloading packages.
>
> --
>
>
>
> _______________________________________________
> Limbo-list mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/limbo-list