knotd exits immediately when logging target is set to /dev/null

Full configuration file in case it matters:

server:    
    rundir: "/tmp"    
    listen: 127.0.0.1@5353    
    
log:    
  - target: /dev/null    
    any: debug    
    
zone:    
  - domain: .    
    storage: .    
    file: "root.zone"  

Unfortunately (but quite understandably) I have no logs to share with you. :)

When the output is redirected in the shell (i.e. knotd -c knot.conf > /dev/null) all goes well.

Do you have any reasonable use case for this? :-)

If you want to disable logging, simply configure empty 'log' section. But still it's possible the server logs something if the logging wasn't configured yet (e.g. configuration parsing error).

The use case indeed was to disable all logging, but it came as a surprise that logging only works to some files.

mentioned in commit e684134a

mentioned in commit 877a13b9

closed with commit 5ca366a9

mentioned in commit 5ca366a9

mentioned in commit 8310c3ee