Re: [knot-dns-users] knot group in a FreeBSD jail -- Permission Denied to Knotc and Python API - knot-dns-users

21 Pro 2018

I don't think the Makefile is wrong.

If you call knotc with an explicit control socket specification, no configuration file is
loaded because it's not needed.
So there is an issue with the configuration access. But I don't understand why knotd
is not affected?
You could also test using configuration database.

Daniel

On 12/21/18 2:44 PM, Rick van Rein wrote:
...
  Hi Daniel,

  I guess it relates to a temporary confdb, which
is created for storing configuration loaded from
 a config file and removed upon. Could you try calling knotc with explicit socket
parameter (knotc -s ...)?  
 Yes, that solved it.

 The default socket path is @run_dir@/knot.sock, and the ports tree
 configures --with-rundir=/var/run/knot but, according to
 https://github.com/freebsd/freebsd-ports/blob/master/dns/knot2/Makefile#L32…
 it is under defined variables.  I will ask Leo if this might need
 correction.

 Thanks!
  -Rick