I see segfaulting too: FreeBSD wasp.2km.casa 12.0-CURRENT FreeBSD 12.0-CURRENT #6 r336229: Fri Jul 13 01:51:31 CEST 2018 r...@wasp.2km.casa:/usr/obj/usr/src/amd64.amd64/sys/GUSTIK amd64 # service local_unbound restart local_unbound not running? (check /var/run/local_unbound.pid). Starting local_unbound. Segmentation fault (core dumped) /etc/rc.d/local_unbound: WARNING: failed to start local_unbound
# du -sh unbound.core 23M unbound.core On Sun, 3 Jun 2018 14:09:45 -0500 Patrick McMunn <doctorwho...@gmail.com> wrote: > I believe the problem of local_unbound segfaulting began after I > compiled the source after the large commit to unbound on Saturday, > May 12, 2018 (about 3 weeks ago). > > I assumed the problem was probably common if I was experiencing it, > but I've seen no other mentions of it. I'm not sure what info I need > to provide, but will do so upon request. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" -- Lars Schotte Mudroňova 13 92101 Piešťany _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
