Date: Sun, 7 Oct 2012 20:33:20 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r39701 - head/en_US.ISO8859-1/articles/hubs Message-ID: <201210072033.q97KXKEF065990@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 are just examples to give you a very rough hint. </para> <para>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210072033.q97KXKEF065990>