On Thu, 2015-03-26 at 12:24 -0400, Bastien Nocera wrote: > ----- Original Message ----- > > On Thu, 2015-03-26 at 10:52 -0500, Dan Williams wrote: > > > On Thu, 2015-03-26 at 10:45 -0500, Michael Catanzaro wrote: > > > > On Wed, 2015-03-25 at 21:02 -0600, Kevin Fenzi wrote: > > > > > This was most likely caused by some issues with out proxy > > > > > servers this evening. We were adding 3 new proxy servers > > > > > into the rotation and there were some config issues with > > > > > some of them. ;( > > > > > > > > > > This would have only affected some folks in North America > > > > > sporadically, (when they happened to hit a proxy that wasn't > > > > > working right) not everyone. > > > > > > > > > > Sorry this happened, everything should be back to normal now. > > > > > > > > I think it would make sense to do a second ping to some other > > > > server if the first one to fedoraproject.org fails, for > > > > robustness. Maybe to redhat.com, or something that should > > > > never be down like google.com (my vote), or to someplace that > > > > promises not to track users, like duckduckgo.com (hardly > > > > matters much for a connectivity check?). > > > > > > We could always use the Google servers that Android uses by > > > default, instead of Fedora :) Those would be pretty well > > > guaranteed to be up... > > > > You might use both so you have less chances of false positive, but > > *please* make it uninstallable, or easily disableable. > > You can edit /etc/NetworkManager/conf.d/20-connectivity-fedora.conf > to disable it. It would probably be better (if NM respects it) to add a higher- numbered file to override it; that way you aren't changing the contents of a packaged file. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
