mirror of
https://github.com/zeek/zeek.git
synced 2025-10-17 14:08:20 +00:00
Revert "Add extract_limit_includes_missing option for file extraction"
This reverts commit f4d0fdcd5c
.
This commit is contained in:
parent
17347df036
commit
5934e143aa
14 changed files with 18 additions and 151 deletions
|
@ -11,15 +11,6 @@ export {
|
|||
## number of bytes). A value of zero means unlimited.
|
||||
option default_limit = 0;
|
||||
|
||||
## This setting configures if the file extract limit is inclusive
|
||||
## of missing bytes. By default, missing bytes do count towards the
|
||||
## limit.
|
||||
## Setting this option to false changes this behavior so that missing
|
||||
## bytes no longer count towards these limits. Files with
|
||||
## missing bytes are created as sparse files on disk. Their apparent size
|
||||
## can exceed this file size limit.
|
||||
option default_limit_includes_missing = T;
|
||||
|
||||
redef record Files::Info += {
|
||||
## Local filename of extracted file.
|
||||
extracted: string &optional &log;
|
||||
|
@ -46,14 +37,6 @@ export {
|
|||
## :zeek:see:`FileExtract::set_limit` is called to increase the
|
||||
## limit. A value of zero means "no limit".
|
||||
extract_limit: count &default=default_limit;
|
||||
## By default, missing bytes in files count towards the extract file size.
|
||||
## Missing bytes can, e.g., occur due to missed traffic, or offsets
|
||||
## used when downloading files.
|
||||
## Setting this option to false changes this behavior so that holes
|
||||
## in files do no longer count towards these limits. Files with
|
||||
## holes are created as sparse files on disk. Their apparent size
|
||||
## can exceed this file size limit.
|
||||
extract_limit_includes_missing: bool &default=default_limit_includes_missing;
|
||||
};
|
||||
|
||||
## Sets the maximum allowed extracted file size.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue