CVSup and anoncvs are going away eventually
Approved by: bcr
This commit is contained in:
parent
cddbaec49a
commit
87d5d64a30
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39701
1 changed files with 4 additions and 7 deletions
|
@ -125,13 +125,10 @@
|
||||||
also affected by the types of services you want to offer.
|
also affected by the types of services you want to offer.
|
||||||
Plain FTP or HTTP services may not require a huge
|
Plain FTP or HTTP services may not require a huge
|
||||||
amount of resources. Watch out if you provide
|
amount of resources. Watch out if you provide
|
||||||
CVSup, rsync or even AnonCVS. This can have a huge
|
rsync. This can have a huge
|
||||||
impact on CPU and memory requirements. Especially
|
impact on CPU and memory requirements as it is
|
||||||
rsync is considered a memory hog, and CVSup does
|
considered a memory hog.
|
||||||
indeed consume some CPU. For AnonCVS it might
|
The following
|
||||||
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
|
|
||||||
are just examples to give you a very rough hint.
|
are just examples to give you a very rough hint.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
|
|
Loading…
Reference in a new issue