Takahiro Kambe writes:
> Hi, this is too late reply.
>
> In message <2532e215-e447-edaa-1f7b-5abf5205f...@netbsd.org>
> on Tue, 24 Apr 2018 07:30:04 +0200,
> Frank Kardel wrote:
>> There are also 2 other observations with a 8.99.12 userland:
>>
>> named has now trouble with
Hi, this is too late reply.
In message <2532e215-e447-edaa-1f7b-5abf5205f...@netbsd.org>
on Tue, 24 Apr 2018 07:30:04 +0200,
Frank Kardel wrote:
> There are also 2 other observations with a 8.99.12 userland:
>
> named has now trouble with interface scanning.
>
>
On 23/04/2018 23:34, Robert Swindells wrote:
Frank Kardel wrote:
using -current as of 20180421 (NetBSD 8.99.14 (GENERIC) #0: Sat Apr 21
23:01:29 UTC 2018
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64)
no cloning interfaces are visible:
gateway#
It is not only a boot time issue - I also see during normal operation:
2018-04-24T10:30:10.466723+00:00 gateway blacklistd 611 - - bl_recv:
recvmsg failed (No buffer space available)
2018-04-24T10:30:10.466821+00:00 gateway blacklistd 611 - - no message
(No buffer space available)
Hi Tom
On 24/04/2018 12:39, Tom Ivar Helbekkmo wrote:
Thomas Klausner writes:
On Tue, Apr 24, 2018 at 08:56:48AM +0100, Roy Marples wrote:
Saying this, from what I'm hearing this only happens at boot time, so we
could potentially shrink the buffer back down again if we need
Thomas Klausner writes:
> On Tue, Apr 24, 2018 at 08:56:48AM +0100, Roy Marples wrote:
>> Saying this, from what I'm hearing this only happens at boot time, so we
>> could potentially shrink the buffer back down again if we need to consider
>> dynamically growing it in the
On Tue, Apr 24, 2018 at 08:56:48AM +0100, Roy Marples wrote:
> Saying this, from what I'm hearing this only happens at boot time, so we
> could potentially shrink the buffer back down again if we need to consider
> dynamically growing it in the kernel as well. No idea if that's even
> possible or
On 24/04/2018 08:26, Martin Husemann wrote:
On Tue, Apr 24, 2018 at 07:30:04AM +0200, Frank Kardel wrote:
syslogd has sometimes issues with /var/run/log
2018-04-24T05:13:34.542548+00:00 gateway syslogd 408 - - recvfrom() unix
`/var/run/log': No buffer space available
This is a seaparate
On Tue, Apr 24, 2018 at 07:30:04AM +0200, Frank Kardel wrote:
> syslogd has sometimes issues with /var/run/log
> 2018-04-24T05:13:34.542548+00:00 gateway syslogd 408 - - recvfrom() unix
> `/var/run/log': No buffer space available
This is a seaparate change and unrelated to compatibility. It
Hi Robert !
That made it work again. I share your view on relative beauty here.
There are also 2 other observations with a 8.99.12 userland:
named has now trouble with interface scanning.
2018-04-24T05:13:34.522295+00:00 gateway named 345 - - automatic
interface scanning terminated: not
Frank Kardel wrote:
>using -current as of 20180421 (NetBSD 8.99.14 (GENERIC) #0: Sat Apr 21
>23:01:29 UTC 2018
>mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64)
>
>no cloning interfaces are visible:
>
>gateway# ifconfig -l
>ixg0 ixg1 ixg2 ixg3 lo0
Hi,
using -current as of 20180421 (NetBSD 8.99.14 (GENERIC) #0: Sat Apr 21
23:01:29 UTC 2018
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64)
no cloning interfaces are visible:
gateway# ifconfig -l
ixg0 ixg1 ixg2 ixg3 lo0 tun0 tun1
gateway# ifconfig -C
ifconfig:
12 matches
Mail list logo