everything is there but app3 and app4<br>(mirrormanager) ill add it today or tomorrow (since im flying to the US in a few hours)<br><br>Paulo<br><br><div><span class="gmail_quote">On 5/29/07, <b class="gmail_sendername">Douglas Furlong
</b> <<a href="mailto:dfurlong@dark-hill.co.uk">dfurlong@dark-hill.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, 2007-05-27 at 18:53 -0500, Mike McGrath wrote:<br>> Karsten Wade wrote:<br>> > On Sun, 2007-05-27 at 17:41 +0100, Damian Myerscough wrote:<br>> ><br>> >> Yea, it would. However mod_easvie is able to detect if users a
<br>> >> continuously hitting refresh<br>> >> to consume bandwidth.<br>> >><br>> ><br>> > Would it make sense to have a few tricks ready to go? Untested or<br>> > unproven items to pull out in response to what happens. Sort of like
<br>> > what Egon Spengler might pull out in Ghostbusters ...<br>> ><br>> > I know, it could be *worse* than whatever happens, but there is a slim<br>> > chance we'll survive.<br>> ><br>>
<br><snip><br>> Unfortunately we don't have full trends from last year because a<br>> different team was running <a href="http://fedora.redhat.com">fedora.redhat.com</a> during the last release<br>> (and
f.rh.c doesn't even exist this release) We'll get a much better<br>> idea of what we're facing on release day.<br><br><snip><br><br>I'm guessing this has been done, but just in case it's not.
<br><br>Do we need to make any changes to cacti for monitoring of services<br>before release? To make sure we do have all of the required trends for<br>next year.<br><br>Doug<br><br>_______________________________________________
<br>Fedora-infrastructure-list mailing list<br><a href="mailto:Fedora-infrastructure-list@redhat.com">Fedora-infrastructure-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list">
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list</a><br><br><br></blockquote></div><br>