Jon Siwek dd173f4961 Always emit scripting errors to stderr during zeek_init ... Otherwise, setting Reporter::errors_to_stderr=F causes important error messages to be lost (and this setting is the default for ZeekCtl). E.g. now that we terminate if there's errors during zeek_init, GH-369 shows that the only error message given was "fatal error: errors occurred while initializing", which is not helpful in determining the actual issue.		2019-05-17 14:18:45 -07:00
..
base	Always emit scripting errors to stderr during zeek_init	2019-05-17 14:18:45 -07:00
policy	More bro-to-zeek renaming in the unit tests	2019-05-16 02:27:54 -05:00
site	More bro-to-zeek renaming in the unit tests	2019-05-16 02:27:54 -05:00
check-test-all-policy.zeek	GH-239: Rename bro to zeek, bro-config to zeek-config, and bro-path-dev to zeek-path-dev.	2019-05-01 21:43:45 +00:00