Suricata

When Suricata 8 is run in user mode with a custom YAML with a custom default-log-dir (ref #3095, #3101, #3762), Suricata writes a bogus error message if current working directory is not writable:

user@system:/> suricata -c ~/mySuricataYAML.yaml -r ~/myPCAP.pcap
Warning: debug: error opening file ./suricata.log: Permission denied
i: suricata: This is Suricata version 8.0.6 RELEASE running in USER mode
E: suricata: The logging directory "." supplied by /home/user/mySuricataYAML.yaml (default-log-dir) is not writable. Shutting down the engine

user@system:/> # huh?? i thought i specified a log dir, not "."... let's see...
user@system:/> grep ^default-log-dir ~/mySuricataYAML.yaml
default-log-dir: /home/user/myLogDir

user@system:/> # wat

No comment on the behaviour of totally ignoring the option; that has been discussed a lot already. But the error message should not be plainly wrong; the default-log-dir supplied by the yaml is NOT ".".