18 Čen
2013
18 Čen
'13
6:56
I see, excellent write up. Well the idea of using AF_UNIX has been a long
time in my backlog,
maybe it's time to finally push it forward. I prefer that to a loopback as
well.
I wouldn't want SGI running for my head, would I?
Kind regards,
Marek
On 17 June 2013 18:26, Robert Edmonds <edmonds(a)debian.org> wrote:
Robert Edmonds wrote:
in general i would recommend using
/var/run/${DAEMON}/${DAEMON}.pid for
pidfiles, creating /var/run/${DAEMON}/ if necessary, owned by the
daemon's uid/gid. then you can use the same directory for lock files,
control sockets, etc.
another tangent: speaking of control sockets, i see that knot uses port
5553 (TCP) for its control socket, which according to IANA is
registered to:
sgi-eventmond 5553 tcp SGI Eventmond Port
BIND8/BIND9 (ndc/rndc) use port 953 for its control socket, which is in
the "well-known" range but appears not to be registered, while unbound
uses port 8953, which is registered:
ub-dns-control 8953 tcp unbound dns nameserver
this is one of the reasons i like AF_UNIX sockets for control sockets :)
--
Robert Edmonds
edmonds(a)debian.org
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users