summaryrefslogtreecommitdiff
path: root/Documentation/config/format.txt
diff options
context:
space:
mode:
authorLibravatar Josh Steadmon <steadmon@google.com>2019-10-04 15:08:20 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-10-05 17:53:51 +0900
commit83e57b04e6ae3bc4c714812768f61bc41b1d56ad (patch)
treef69fe2fc112bc82526d0d230cf47403230e623e4 /Documentation/config/format.txt
parentdocs: clarify trace2 version invariants (diff)
downloadtgif-83e57b04e6ae3bc4c714812768f61bc41b1d56ad.tar.xz
trace2: discard new traces if target directory has too many files
trace2 can write files into a target directory. With heavy usage, this directory can fill up with files, causing difficulty for trace-processing systems. This patch adds a config option (trace2.maxFiles) to set a maximum number of files that trace2 will write to a target directory. The following behavior is enabled when the maxFiles is set to a positive integer: When trace2 would write a file to a target directory, first check whether or not the traces should be discarded. Traces should be discarded if: * there is a sentinel file declaring that there are too many files * OR, the number of files exceeds trace2.maxFiles. In the latter case, we create a sentinel file named git-trace2-discard to speed up future checks. The assumption is that a separate trace-processing system is dealing with the generated traces; once it processes and removes the sentinel file, it should be safe to generate new trace files again. The default value for trace2.maxFiles is zero, which disables the file count check. The config can also be overridden with a new environment variable: GIT_TRACE2_MAX_FILES. Signed-off-by: Josh Steadmon <steadmon@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/config/format.txt')
0 files changed, 0 insertions, 0 deletions