Date: Wed, 30 Nov 2022 16:50:23 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262995] dns/unbound: Not recorded in syslogd Message-ID: <bug-262995-7788-AfAMBJOKOv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262995-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-262995-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=3D262995 Richard Russo <freebsd@ruka.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@ruka.org --- Comment #13 from Richard Russo <freebsd@ruka.org> --- I'm not sure if it's part of the syslog issue, but the rc change in the 1.1= 7.0 port causes unbound to be first in rcorder instead of the same time as local_unbound, (seen on 13.1-RELEASE-p5) moving the load_rc_config line back so it's ahead of the defaults fixed my issue=20 link to the rc change:=20 https://cgit.freebsd.org/ports/commit/?id=3D7b0d6de05baabfbcd7a25fd0440ee3b= f1f3bc23e FWIW, re: syslog, on my FreeBSD 13.1 system, and skipping unrelated scripts: /etc/rc.d/syslogd /etc/rc.d/SERVERS /etc/rc.d/local_unbound /usr/local/etc/rc.d/unbound /etc/rc.d/NETWORKING So perhaps changes to syslogd or other rc files in base may have fixed the issue (assuming unbound from ports doesn't start first, like it did after upgrading) --=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-262995-7788-AfAMBJOKOv>