21 Čec
21 Čec
11:45
Hello!
On 07/21/2017 11:31 AM, Yoshihito Horigome wrote:
/usr/sbin/kresd -c /etc/knot-resolver/kresd.conf -v -f
4 -k
/etc/knot-resolver/root.key /var/knot-resolver
I don't immediately see what happens in your case, but so far kresd does
not support running under systemd supervision with multiple forks. It's
actually supposed to print a descriptive error and exit if that
configuration is detected. See also
https://gitlab.labs.nic.cz/knot/knot-resolver/issues/85#note_50539
--Vladimir
12:00
On 07/21/2017 11:51 AM, Yoshihito Horigome wrote:
Thank you for the information.
Is fork still to be an experimental parameter?
As it is commonly used, it is not mandatory as myself, so for the
moment I think whether to deal with the parameter removed.
If you run kresd without (direct) systemd supervision, the -f parameter
should work well, even though it's a setup that doesn't currently get as
much testing as the single-process mode. You can also simply run
multiple kresd instances over the same cache - the only difference is
missing a shared communication channel, in particular the `map` lua
function that runs a lua command in all the connected instances.
--Vladimir
2481
days inactive
2481
days old
4 comments
2 participants
participants (2)
-
Vladimír Čunát -
Yoshihito Horigome