Dear Knot developers, I've been playing with Knot version 1.2.0-rc3, and run into a small issue. Apologies if it has already been reported. I'm using a configuration like this: system { ... ... user knot.knot; } log { file "/var/log/knot/knot.log" { ... } } When I start Knot, it starts running as root, and creates the file /var/log/knot/knot.log, as root. It then switches to the non-privileged user "knot". Now it can no longer continue writing to the log file. Could you please add some code (to go before it changes the UID) to change the ownership of the log file to the user it is about to switch to? Regards, Anand _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

On 08/03/2013 23:24, Ondřej Surý wrote: Hi Ondrej, If the log file is created after privileges are dropped, then the first few log entries (such as binding to interface) would have nowhere to go. So you should still consider changing the ownership just before dropping privileges. As a compromise, perhaps Knot could log those lines to syslog, and then switch to the log file (similar to what BIND does on startup), but that's kind of messy too, with log entries in different places. Regards, Anand _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users