Date: Tue, 15 Dec 2020 22:25:25 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251821] dns/unbound: SIGSEGV in 1.13.0 Message-ID: <bug-251821-7788-4dlBy58hBl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251821-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-251821-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=3D251821 --- Comment #12 from Tatsuki Makino <tatsuki_makino@hotmail.com> --- I rebooted FreeBSD and unbound was started cleanly by /etc/rc. In this case, the process that was started at that time is still working. If we use sockstat -4 -6 -c -P tcp,udp -s to check that there are many sock= ets created by unbound (including the one that unbound gave away) and then rest= art unbound, we are likely to have this problem. By the way, services/outside_network.c has added reuse_foobar :) between 1.= 12.0 and 1.13.0. How does a new process know that a socket created by an old process is still unusable? --=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-251821-7788-4dlBy58hBl>