CVSup is going bye-bye.
Approved by: bcr
This commit is contained in:
parent
3c176e016d
commit
8abedaba27
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39686
1 changed files with 0 additions and 23 deletions
|
@ -10152,29 +10152,6 @@ hint.sio.7.irq="12"</programlisting>
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="cvsup-round-robin">
|
||||
<para>Why isn't <hostid role="fqdn">cvsup.FreeBSD.org</hostid>
|
||||
a round robin DNS entry to share the load amongst the various
|
||||
<application>CVSup</application> servers?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>While <application>CVSup</application> mirrors update
|
||||
from the master <application>CVSup</application> server
|
||||
hourly, this update might happen at any time during the
|
||||
hour. This means that some servers have newer code than
|
||||
others, even though all servers have code that is less than
|
||||
an hour old. If <hostid
|
||||
role="fqdn">cvsup.FreeBSD.org</hostid> was a round robin
|
||||
DNS entry that simply redirected users to a random
|
||||
<application>CVSup</application> server, running
|
||||
<application>CVSup</application> twice in a row could
|
||||
download code older than the code already on the
|
||||
system.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="ctm">
|
||||
<para>Can I follow <emphasis>-CURRENT</emphasis> with limited
|
||||
|
|
Loading…
Reference in a new issue