On Jul 22, 4:42 pm, Jan Groenewald <j...@aims.ac.za> wrote: > Perhaps the random > noise is enough of randomness...?
not for me here, it was always the same (CH). > > You test this by opening index.html? Everything here is > proxied, and in low bandwidth environments HAVE to be proxied. > By policy and techically enforced. i've never heard of that before. perhaps it's possible to bypass a proxy as an argument to the urllib call. > Also, I would print the actual command to run: > sage -upgrade http://... that won't work, i just looked at the sage-upgrade script. it appends "/spkg" to the SAGE_SERVER env variable and then does funny things. I've moved the directory on the mirror to ".../spkg/standard" to get this in sync as a first step. Then it might work but not tested. I want this integrated into sage-upgrade. > > A ping time would be better than opening. We have pings in the country of > 1-100ms > and through to Europe/US at 400-800. > (Debian does this, I think, and mistakenly keeps giving me mirrors in Eastern > Europe) > Then again some servers don't allow pings... as you said, my tests showed that pinging doesn't work for all of them and well, perhaps downloading some bogus 100kb file would be more accurate, but why wasting so much traffic. > And really, as a sysadm, I found out which mirror to use. > I was more thinking about the end user who wants it transparantly. > But this is a good start! me too, that's why it is in "sage-devel" and it's not for the enduser. btw: the list is so short, because it is once again mirroring out to all mirrors. the list will be normal if all are in sync. http://sagemath.org/mirror_manager.txt thx for testing. h --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
