generation of loaded_scripts.log

Why does this occur if I run using "local tuning/track-all-assets", but
not if I run with just "tuning/track-all-assets"? I don't understand
why dumping out the loaded scripts only matters for "local", though
maybe the notion is that with "local" it's hard to track just what
might get loaded .... ?

    Vern

The local script is where we are suggesting a starting configuration for users, similarly to how Apache probably ships a default httpd.conf. The misc/loaded-scripts script is loaded in the local script.

  .Seth

The local script is where we are suggesting a starting configuration for
users, similarly to how Apache probably ships a default httpd.conf.

Right, I gathered that.

The misc/loaded-scripts script is loaded in the local script.

This is the part that's not so obvious to me. I guess the rationale
is "who knows what junk might be in local/ ...." ?

    Vern

Basically. Do you think that local.bro should be more well defined?

  .Seth

>> The misc/loaded-scripts script is loaded in the local script.
>
> This is the part that's not so obvious to me. I guess the rationale
> is "who knows what junk might be in local/ ...." ?

Basically. Do you think that local.bro should be more well defined?

No, I just am not sure I see that it's grab-bag nature means that
misc/loaded-scripts should necessarily be itself loaded. But if
you think it's appropriate to do so, it's okay by me.

    Vern