Re: DNSSEC/Log Spam for partially DNSSEC domain

2018-06-29 Thread Larry Rosenman
On Fri, Jun 29, 2018 at 07:33:02PM -0700, Michael Mitchell wrote: > /etc/syslog.conf maybe > > mdm - from a phone > That won't help, as I don't want to suppress ALL of the nastygrams. I'm looking for more selectivity from this in libc. -- Larry Rosenman

Re: DNSSEC/Log Spam for partially DNSSEC domain

2018-06-29 Thread Larry Rosenman
On Fri, Jun 29, 2018 at 08:29:48PM -0700, Michael Mitchell wrote: > pick the right options for the daemon and info level? Nope, it's just this message which is annoying. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail:

Re: DNSSEC/Log Spam for partially DNSSEC domain

2018-06-29 Thread Michael Mitchell
pick the right options for the daemon and info level? mdm - from a phone On Fri, Jun 29, 2018, 8:00 PM Larry Rosenman wrote: > On Fri, Jun 29, 2018 at 07:33:02PM -0700, Michael Mitchell wrote: > > /etc/syslog.conf maybe > > > > mdm - from a phone > > > That won't help, as I don't want to

Re: DNSSEC/Log Spam for partially DNSSEC domain

2018-06-29 Thread Michael Mitchell
/etc/syslog.conf maybe mdm - from a phone On Fri, Jun 29, 2018, 7:27 PM Larry Rosenman wrote: > I'm running Exim, with DNSSEC enabled, and my zone (lerctr.org) is > DNSSEC signed, but my dyn.lerctr.org subdomain is NOT DNSSEC signed due > to HE.net don't support DNSSEC. > > I get a ton of: >

DNSSEC/Log Spam for partially DNSSEC domain

2018-06-29 Thread Larry Rosenman
I'm running Exim, with DNSSEC enabled, and my zone (lerctr.org) is DNSSEC signed, but my dyn.lerctr.org subdomain is NOT DNSSEC signed due to HE.net don't support DNSSEC. I get a ton of: Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked for "borg.lerctr.org IN ", got

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread Ryan Libby
[Re-sending from my subscription address, sorry for the spam] On Fri, Jun 29, 2018 at 1:26 PM, John Baldwin wrote: > On 6/28/18 7:54 PM, Mark Millard wrote: >> On 2018-Jun-28, at 6:04 PM, Mark Millard wrote: >> >>> On 2018-Jun-28, at 5:39 PM, Mark Millard wrote: >>> [ ci.free.bsd.org

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread Mark Millard
On 2018-Jun-29, at 2:37 PM, Mark Millard wrote: > [I expect this is more than just amd64-gcc related but that is all > that ci.freebsd.org normally builds via a devel/*-gcc .] > > On 2018-Jun-29, at 10:38 AM, John Baldwin wrote: > >> On 6/28/18 7:54 PM, Mark Millard wrote: >>> On 2018-Jun-28,

Re: RiscV tinderbox fails

2018-06-29 Thread blubee blubeeme
It seems to be that the FreeBSD implementation of the RISC-V has stalled and development is only proceeding on Linux with GCC. In my opinion FreeBSD forget GCC and work on implementing RISC-V backend for the llvm project. On Sat, Jun 30, 2018, 08:18 Dimitry Andric wrote: > On 29 Jun 2018, at

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread Ryan Libby
On Fri, Jun 29, 2018 at 1:26 PM, John Baldwin wrote: > On 6/28/18 7:54 PM, Mark Millard wrote: >> On 2018-Jun-28, at 6:04 PM, Mark Millard wrote: >> >>> On 2018-Jun-28, at 5:39 PM, Mark Millard wrote: >>> [ ci.free.bsd.org jumped from -r335773 (built) to -r335784 (failed) for

Re: RiscV tinderbox fails

2018-06-29 Thread Dimitry Andric
On 29 Jun 2018, at 13:33, hartmut.bra...@dlr.de wrote: > > is it supposed not to fail? I get: > > /usr/obj/usr/src/riscv.riscv64sf/tmp/usr/lib/libgcc.a(comparedf2.o): In > function > `__gedf2': > /usr/src/contrib/compiler-rt/lib/builtins/comparedf2.c:101: multiple > definition > of `__gedf2' >

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread Mark Millard
[I expect this is more than just amd64-gcc related but that is all that ci.freebsd.org normally builds via a devel/*-gcc .] On 2018-Jun-29, at 10:38 AM, John Baldwin wrote: > On 6/28/18 7:54 PM, Mark Millard wrote: >> On 2018-Jun-28, at 6:04 PM, Mark Millard wrote: >> >>> On 2018-Jun-28, at

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread John Baldwin
On 6/28/18 7:54 PM, Mark Millard wrote: > On 2018-Jun-28, at 6:04 PM, Mark Millard wrote: > >> On 2018-Jun-28, at 5:39 PM, Mark Millard wrote: >> >>> [ ci.free.bsd.org jumped from -r335773 (built) to -r335784 (failed) >>> for FreeBSD-head-amd64-gcc. It looked to me like the most likely >>>

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread John Baldwin
On 6/28/18 7:54 PM, Mark Millard wrote: > On 2018-Jun-28, at 6:04 PM, Mark Millard wrote: > >> On 2018-Jun-28, at 5:39 PM, Mark Millard wrote: >> >>> [ ci.free.bsd.org jumped from -r335773 (built) to -r335784 (failed) >>> for FreeBSD-head-amd64-gcc. It looked to me like the most likely >>>

Re: head -r335795 broke the builds for ci.freebsd.org 's FreeBSD-head-{amd64,i386,powerpc,risc64,sparc64}-build

2018-06-29 Thread Sean Bruno
On 06/29/18 08:50, Mark Millard wrote: > Side note: > > All I get for the lists that I normally look at is: > > Error 503 Backend fetch failed > > Backend status: Backend fetch failed > > Transaction ID: . . . I think I fixed that about an hour ago. Try again. sean signature.asc

head -r335795 broke the builds for ci.freebsd.org 's FreeBSD-head-{amd64,i386,powerpc,risc64,sparc64}-build

2018-06-29 Thread Mark Millard
clang example: ( https://ci.freebsd.org/job/FreeBSD-head-amd64-build/9257/consoleText ) --- key_debug.o --- /usr/src/sys/netipsec/key_debug.c:89:1: error: no previous prototype for function 'kdebug_sadb_type' [-Werror,-Wmissing-prototypes] kdebug_sadb_type(uint8_t type) ^

RiscV tinderbox fails

2018-06-29 Thread Hartmut.Brandt
Hi, is it supposed not to fail? I get: /usr/obj/usr/src/riscv.riscv64sf/tmp/usr/lib/libgcc.a(comparedf2.o): In function `__gedf2': /usr/src/contrib/compiler-rt/lib/builtins/comparedf2.c:101: multiple definition of `__gedf2'

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

2018-06-29 Thread Toomas Soome
> On 29 Jun 2018, at 05:47, KIRIYAMA Kazuhiko wrote: > > At Tue, 26 Jun 2018 09:48:10 +0300, > Toomas Soome wrote: >> >> >> >>> On 26 Jun 2018, at 05:08, KIRIYAMA Kazuhiko wrote: >>> >>> At Thu, 21 Jun 2018 10:48:28 +0300, >>> Toomas Soome wrote: > On 21 Jun 2018, at