# HG changeset patch
# User amazy
# Date 1500461396 -7200
# Node ID 7063afe5748ce8bc3f214c49fc3fb51ad39e48a8
# Parent  268ec482f05155d6415d8ab7ed626a7929dd6bd9
added info about recycling

diff -r 268ec482f051 -r 7063afe5748c Sphinx/source/faq/features.rst
--- a/Sphinx/source/faq/features.rst	Thu Jul 13 13:05:54 2017 +0200
+++ b/Sphinx/source/faq/features.rst	Wed Jul 19 12:49:56 2017 +0200
@@ -35,11 +35,14 @@
 time inside Orthanc can be automatically deleted when the disk space
 used by Orthanc grows above a threshold, or when the number of stored
 patients grows above a threshold. This feature enables the automated
-control of the disk space dedicated to Orthanc.
+control of the disk space dedicated to Orthanc.  Note that pushing a 
+new study for an existing patient will not change its position in the
+recycling order.
 
 Recycling is controlled by the ``MaximumStorageSize`` and the
 ``MaximumPatientCount`` options in the :ref:`Orthanc configuration
-file <configuration>`.
+file <configuration>`.  Setting both these values to 0 will disable 
+recycling.
 
 It is possible to prevent important data from being automatically
 recycled. This mechanism is called **protection**. Each patient can be
@@ -54,7 +57,6 @@
 study/series that is part of the same patient might lead to a loss in
 consistency with respect to the medical history of this patient.
 
-
 .. _compression:
 
 Compression