Actions
Bug #1911
closed
AT
JI
Commandline provided configuration values don't persist after initial startup
Bug #1911:
Commandline provided configuration values don't persist after initial startup
Affected Versions:
Effort:
Difficulty:
Label:
Description
When using --set key=value commandline arguments to set some configuration parameters on startup, it seems that those values are not carried across reloads.
What I'd expect would happen:
# suricata ... --set default-rule-path=/some/path kill -USR2 suricata_pid <suricata reloads normally, reading rules from /some/path>
What actually happens
# suricata ... --set default-rule-path=/some/path kill -USR2 _suricata_pid <suricata reloads normally, reading rules from default (compiled in) /etc/suricata/rules but due to wrong directory in regard of --set argument, the rule files aren't found -> operation continues with empty ruleset>
Actions