Date: Mon, 01 Jul 2024 13:00:23 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 277540] dns/knot-resolver: fixing rc scripts krescachegc and kresd Message-ID: <bug-277540-7788-IVbgy50VbS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277540-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-277540-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277540 --- Comment #1 from Leo Vandewoestijne <freebsd@dns.company> --- Created attachment 251816 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D251816&action= =3Dedit knot-resolver rc I delved in this report numerous time, but never was able to solve everythi= ng at once, as there is a number of problems/conflicts within just a few lines. - /var/run/kresd is created as kresd, with wrong permissions, which are overwritten in kresd's rc script at the start routine. - /var/run/kresd needs to be 700 or else krescachegc will complain it's not existing or not an LMDB dir. - daemon (for kresd) needs to be running as root - I guess because above re= ason - kresd however is running as kresd (if you tell so in it's config). - daemon (for krescachegc) can be running as kresd (...?) '-c <resolver_cache>' is indeed something which became problematic. status_cmd=3D"${name}_status" indeed was missing, while the routine was in = place. However, -AFAIK- in krescachegc's rc script there is no need to have explic= it start/stop/status routine. Although it could be added if there is a good reason for it. As far as I could test this patch would/should solve all the mentioned issu= es. All feedback is appreciated. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277540-7788-IVbgy50VbS>