Date: Tue, 16 Jul 2024 14:31:44 +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-h0tzVLs8m3@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 #5 from Michael Grimm <trashcan@ellael.org> --- After applying your patch #252079 I installed knot-resolver in a vanilla te= st jail, applied 'service kresd start', and ended up with: MW-test|root> la /var/run/kresd/ drwxr-x--- 2 root kresd uarch 3 Jul 16 16:03 control -rw-r----- 1 root kresd uarch 10485760 Jul 16 16:08 data.mdb -rw-r----- 1 root kresd uarch 8192 Jul 16 16:03 lock.mdb I don't understand why, but user is still root for both mdb files! Tries some restart operations, but ownership remains root, not to my surpri= se. And starting krescachegc results in the already reported error messages.=20 Understandable, as krescachegc runs as user kresd and cannot access both fi= les. BUT: If I do run krescachegc as root [1], krescachegc stops complaining. I don't know, if that will be ok, though. [1] command_args=3D"-c -f -r -S -T ${name} -- ${procname} -c ${kresd_rundir= } -d ${krescachegc_millis}" Last, but not least, knot-resolver-5.7.3 is out: TIMESTAMP =3D 1721139599 SHA256 (knot-resolver-5.7.3.tar.xz) =3D efc6e45ffc5efd98921ea5cd3fece166a1a5ce9eaa12d41b46268964353dbedb SIZE (knot-resolver-5.7.3.tar.xz) =3D 1930732 Compiles and runs as expected. Regards,=20 Michael --=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-h0tzVLs8m3>