[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 --- Comment #7 from vfx...@gmail.com --- --- The following script could handle it -- /etc/rc.d/local_unbound_syslog -- #!/bin/sh # PROVIDE: local_unbound_syslog # REQUIRE: local_unbound syslogd . /etc/rc.subr name="local_unbound_syslog"

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 --- Comment #6 from vfx...@gmail.com --- The relationship between syslogd and local-unboun is as follows /etc/rc.d/local_unbound # PROVIDE: local_unbound # REQUIRE: FILESYSTEMS defaultroute netwait resolv # BEFORE: NETWORKING /etc/rc.d/

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 --- Comment #5 from Chris Hutchinson --- Just a thought. But does the rc script that comes with the port have a depends on syslog? IOW if the script can't find syslog already running, it should bail w/ message: syslog can't be found or not

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 --- Comment #4 from Jaap Akkerhuis --- I don't maintain this part of the base system so don't ask me. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 --- Comment #3 from vfx...@gmail.com --- (In reply to Jaap Akkerhuis from comment #2) Confirmed fail. It is chrooted by default, so log_reopen does not solve the problem. man 8 unbound-contro log_reopen >(which may not work if chrooted).

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 Jaap Akkerhuis changed: What|Removed |Added CC||j...@nlnetlabs.nl --- Comment #2

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 --- Comment #1 from vfx...@gmail.com --- /var/log/console.log kernel: Starting local_unbound. kernel: Waiting for nameserver to start... good -- Unbound can not record log because syslogd has not started kernel: Updating /var/run/os-re

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-04-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 vfx...@gmail.com changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-03-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 vfx...@gmail.com changed: What|Removed |Added Severity|Affects Only Me |Affects Many People -- You are

[Bug 262844] Not recorded in syslog unless local-unbound is restarted

2022-03-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262844 Bug ID: 262844 Summary: Not recorded in syslog unless local-unbound is restarted Product: Base System Version: 12.3-RELEASE Hardware: Any OS: Any