[Bug 256221] dns/knot-resolver: the kresd init script won't stop the service

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 14 Jun 2021 17:43:41 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256221

--- Comment #20 from Chris Hutchinson <portmaster_at_bsdforge.com> ---
(In reply to Vladimír Čunát from comment #19)
> The registration problem was worked around within a few hours (reportedly),
> but I don't really get what you're about to submit.  I don't think it makes
> sense for us (upstream) to include the FreeBSD init scripts, as none of us
> knows about writing (FreeBSD) init scripts and we can't directly affect
> their packages/ports anyway.
Thanks for your efforts, Vladimír!
Sure. Probably better to keep it local (here) to the FreeBSD ports.

> By the way, finding out PID by a `ps` call feels a bit fragile to me
> (though I expect it's better to get some improvement than nothing).
> I assumed that the pidfiles are meant to keep this state, but I don't
> really know init script stuff...
Wouldn't have been my first choice either. But, given the use of daemon(8).
We end up with 2 pids...
/var/run/kresd/kresd.pid &&
/var/run/kresd/control/<procnum>.pid
and worse; different versions of knot-resolver result in a differently
named kresd subdir. But to my credit, it always works as intended. :-)
The _correct_ solution would be to remove systemd, and use proper sysV
initialization. Or _add_ it;
#ifdef (FreeBSD...

But until, or unless... this gets the job done.

Thanks again, Vladimír.

--Chris

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Mon Jun 14 2021 - 17:43:41 UTC

Original text of this message