svn commit: r39701 - head/en_US.ISO8859-1/articles/hubs

[Benjamin Kaduk]

On Sun, 7 Oct 2012, Eitan Adler wrote:

> Author: eadler (src,ports committer)
> Date: Sun Oct  7 20:33:19 2012
> New Revision: 39701
> URL: http://svn.freebsd.org/changeset/doc/39701
>
> Log:
>  CVSup and anoncvs are going away eventually
>
>  Approved by:	bcr
>
> Modified:
>  head/en_US.ISO8859-1/articles/hubs/article.xml
>
> Modified: head/en_US.ISO8859-1/articles/hubs/article.xml
> ==============================================================================
> --- head/en_US.ISO8859-1/articles/hubs/article.xml	Sun Oct  7 20:33:16 2012	(r39700)
> +++ head/en_US.ISO8859-1/articles/hubs/article.xml	Sun Oct  7 20:33:19 2012	(r39701)
> @@ -125,13 +125,10 @@
>         also affected by the types of services you want to offer.
>         Plain FTP or HTTP services may not require a huge
>         amount of resources. Watch out if you provide
> -        CVSup, rsync or even AnonCVS. This can have a huge
> -        impact on CPU and memory requirements. Especially
> -        rsync is considered a memory hog, and CVSup does
> -        indeed consume some CPU. For AnonCVS it might
> -        be a nice idea to set up a memory resident file system (MFS) of at least
> -        300 MB, so you need to take this into account
> -        for your memory requirements. The following
> +        rsync. This can have a huge
> +        impact on CPU and memory requirements as it is
> +        considered a memory hog.
> +        The following

The claim that rsync is a memory hog dates from its addition in 2002.
I do not believe (especially given modern hardware specs) that the claim 
is still accurate, since modern versions of rsync have changed the 
algorithm used so as to not suffer from this flaw.

This change is just swapping wrong for differently wrong, and should be 
revisited.

-Ben Kaduk