modules/dnstap: don't do anything on loading the module
Usually in configuration the module is loaded in a separate command from passing configuration to it. For dnstap this loading would immediately lead to opening the default socket path, even if the configuration actually specifies (a different) path later. Users can still force using the default by passing an empty table: `dnstap.config({})` or `modules = { dnstap = {}}` (though I doubt the utility of the default /tmp/dnstap.sock anyway)
Please register or sign in to comment