On Thu, Feb 14, 2019 at 10:13 AM Kevin Oberman wrote:
> On Thu, Feb 14, 2019 at 3:10 AM Pete French
> wrote:
> > On 14/02/2019 01:43, Jason Tubnor wrote:
> > > I also have hit this IPv6 issue (I thought I was going crazy until I
> > worked
> > > it out) and other iflib issues in 12.0, which have
On Thu, Feb 14, 2019 at 3:10 AM Pete French
wrote:
>
>
> On 14/02/2019 01:43, Jason Tubnor wrote:
> > I also have hit this IPv6 issue (I thought I was going crazy until I
> worked
> > it out) and other iflib issues in 12.0, which have been fixed in -STABLE
> > that really should be patched in 12.
Am 13.02.19 um 10:59 schrieb Andriy Gapon:
> On 12/02/2019 20:17, Eugene Grosbein wrote:
>> 13.02.2019 1:14, Eugene Grosbein wrote:
>>
>>> Use following command to see how much memory is wasted in your case:
>>>
>>> vmstat -z | awk -F, '{printf "%10s %s\n", $2*$5/1024/1024, $1}' | sort
>>> -k1,1 -
(bcc -current and -stable for more audience)
FreeBSD CI Weekly Report 2019-02-10
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-02-04 to 2019-02-10.
During this period, we have:
* 2564 builds (97.4% passed, 2.6% faile
On 14/02/2019 01:43, Jason Tubnor wrote:
I also have hit this IPv6 issue (I thought I was going crazy until I worked
it out) and other iflib issues in 12.0, which have been fixed in -STABLE
that really should be patched in 12.0 or bring forward an early 12.1
release. For our use case, 12.0 is
