@manuel beat me to this but let me see if I can assist them. This post you may find helpful:
Let us work backward for a second in respect to your post.
This is up to you. You can use one, both, or none.
Think of reflector-simple as one shop stopping. You set it up once and forget it. This means you will have a static mirror list that never changes ranked according to the options you selected via the button in the welcome app. This is made easier by having the check boxes for number of mirrors, rate (speed), and how long the mirrors refreshed last. This will not change unless you repeat the process manually.
Think of reflector-auto as a way to automatically repeat this process on a timer as a service running in the background. This is slightly more complicated because here we don’t have the handy check boxes and have to add the options manually to a file that the reflector-auto.timer service will execute automatically based on the options you have added into the file /etc/reflector-auto.conf file. So you set the options in the file by manually adding them (type them in) and the service runs the file on a timer.
Once you set the .conf and enable the timer it should just run.
Here is an example file:
## Configuration for 'reflector-auto'.
-c sets the country. So the first two look for mirrors in the US and Canada.
-p sets the protocol (there is also a checkbox for this in reflector-simple) I only use https
-a sets how many hours since the mirror last refreshed. The example uses 4 I use 2.
-f how many mirrors you would like to pull in to use.
–sort rate (speed).
@manuel if I have said anything wrong here please correct.
Reflector devs have added a similar systemd integration to reflector what EndeavourOS has in reflector-auto.
Because of that, there’s no reason to develop reflector-auto further (unless someone has a really great new idea for it ).
So I’ll keep reflector-auto available for a while (i.e. until the end of year 2020 at least), but eventually it is bound to be replaced with the similar feature of reflector.
I’ll update the EndeavourOS wiki too about this new turn of events.
Not that it’s a big problem but curious:
It is set to be within 1 second BUT have a random +12 hours. Seems overkill to have a 1 second accuracy if you have that random margin…
(Reading the systemd wiki it’s said a setting like this is to avoid workload spikes for scheduled tasks, but that seems to be a server issue, mostly.)
So, changed that random delay to 1 hour. No need of having it randomly switch day of the week within the first well… week.