I'm Harry, and I want to be public mirror host for Fedora EPEL.
I have 2 server in Indonesia region. Supported by 10G bandwidth.
Sponsor Organization: DomaiNesia
- URL Sponsor: https://www.domainesia.com
- IPv4 Addr: 184.108.40.206
- IPv6 Addr: 2001:df7:5300:2::64
- Hostname Mirror: linux.domainesia.com/fedora/ (http, https, rsync)
Sponsor Organization: NevaCloud
- URL Sponsor: https://nevacloud.com
- IPv4 Addr: 220.127.116.11
- IPv6 Addr: 2001:df7:5300:2::63
- Hostname Mirror: mirror.nevacloud.com/fedora/ (http, https, rsync)
Please help for the next step.
I have a question regarding mirror manager information about our mirror. In december we had a HW failure on our mirror and we probably got disabled from mirror list (if it wasn’t disabled even earlier). As I see it on e.g. RockyLinux MirrorManager, it has to be manually reenabled again. We still keep mirror data-wise, but we are not serving any traffic = wasted space.
Could you please tell us, what administrative account (if any) is used for mirror ftp.sh.cvut.cz (to know whom to contact to get access or how to login to mirror manager) or if we should create new account to administer our mirror participance?
Network & System Administrator
www.siliconhill.cz / sh.cvut.cz
Currently this defaults to 3. I have seen people online suggesting that they
get better performance setting it to 6 (or higher).
As mirror admins in 2022, do you care? Do you have a preference for our
default? Note that I'm 87% sure that GNOME Software does not do parallel
downloads so this would primarily affect server/cloud use cases (the later
of which should hit cloud-provider mirrors) and enthusiast usage.
Fedora Project Leader
introducing yourself, stating you would like to become a mirror, your IP
address, your location (country), and your outbound bandwidth available
for the mirror. Private mirrors are encouraged to send a similar note.
We would like to become a mirror.
IP : 18.104.22.168
https://mangohost.net/ | hostmaster(a)mangohost.net