Christian Kreibich 3f02c0a67c Source file path control for Input and Intel frameworks ... This introduces the following redefinable string constants, empty by default: - InputAscii::path_prefix - InputBinary::path_prefix - Intel::path_prefix When using ASCII or binary reades in the Input/Intel Framework with an input stream source that does not have an absolute path, these constants cause Zeek to prefix the resulting paths accordingly. For example, in the following the location on disk from which Zeek loads the input becomes "/path/to/input/whitelist.data": redef InputAscii::path_prefix = "/path/to/input"; event bro_init() { Input::add_table([$source="whitelist.data", ...]); } These path prefixes can be absolute or relative. When an input stream source already uses an absolute path, this path is preserved and the new variables have no effect (i.e., we do not affect configurations already using absolute paths). Since the Intel framework builds upon the Input framework, the first two paths also affect Intel file locations. If this is undesirable, the Intel::path_prefix variable allows specifying a separate path: when its value is absolute, the resulting source seen by the Input framework is absolute, therefore no further changes to the paths happen.		2019-03-15 16:43:36 -07:00
..
output	Source file path control for Input and Intel frameworks	2019-03-15 16:43:36 -07:00