Tweak min-free/max-free descriptions
This commit is contained in:
parent
41d010fff6
commit
320126aeeb
1 changed files with 9 additions and 5 deletions
|
@ -483,8 +483,10 @@ builtins.fetchurl {
|
||||||
|
|
||||||
<varlistentry xml:id="conf-max-free"><term><literal>max-free</literal></term>
|
<varlistentry xml:id="conf-max-free"><term><literal>max-free</literal></term>
|
||||||
|
|
||||||
<listitem><para>This option defines after how many free bytes to stop collecting
|
<listitem><para>When a garbage collection is triggered by the
|
||||||
garbage once the <literal>min-free</literal> condition gets triggered.</para></listitem>
|
<literal>min-free</literal> option, it stops as soon as
|
||||||
|
<literal>max-free</literal> bytes are available. The default is
|
||||||
|
infinity (i.e. delete all garbage).</para></listitem>
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
@ -528,9 +530,11 @@ builtins.fetchurl {
|
||||||
<varlistentry xml:id="conf-min-free"><term><literal>min-free</literal></term>
|
<varlistentry xml:id="conf-min-free"><term><literal>min-free</literal></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>When the disk reaches <literal>min-free</literal> bytes of free disk space during a build, nix
|
<para>When free disk space in <filename>/nix/store</filename>
|
||||||
will start to garbage-collection until <literal>max-free</literal> bytes are available on the disk.
|
drops below <literal>min-free</literal> during a build, Nix
|
||||||
A value of <literal>0</literal> (the default) means that this feature is disabled.</para>
|
performs a garbage-collection until <literal>max-free</literal>
|
||||||
|
bytes are available or there is no more garbage. A value of
|
||||||
|
<literal>0</literal> (the default) disables this feature.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
Loading…
Reference in a new issue