On 7/25/2019 12:09 PM, Dimitry Andric wrote:
> Hmmm, is the logic reversed somehow ? The good news is if nothing is
>>> defined, it does the right thing.
>> The idea is that the default is to *not* bootstrap the compiler, if the
>> system compiler is new enough. E.g. if you build r350256 from a
On Thu, Jul 25, 2019 at 9:46 AM Kyle Evans wrote:
>
> On Thu, Jul 25, 2019 at 9:41 AM Trond Endrestøl
> wrote:
> >
> > Hi,
> >
> > I have a VPN service running net/ocserv 0.12.4_1. Everything is ok
> > until the first client disconnects. The main ocserv process hangs
> > while destroying the tun
Hi Marco and Adam,
Thanks for the responses. Answers to your questions are inline
On Sat, Jul 20, 2019 at 06:56:19PM +0200, Marco Steinbach wrote:
> I've outfitted all of them with 4-port Intel PRO/1000 PCIe driven by
> igb(4), and am not using the onboard re(4) NICs.
We use the onboard
On 24 Jul 2019, at 23:21, Dimitry Andric wrote:
>
> On 24 Jul 2019, at 22:56, mike tancsa wrote:
>>
>> On 7/24/2019 1:21 PM, mike tancsa wrote:
>>> On 7/24/2019 12:02 PM, Dimitry Andric wrote:
> ...
>>> # cat /etc/src.conf /etc/make.conf
>>> MK_SYSTEM_COMPILER=no
>>> MK_SYSTEM_LINKER=no
>>>
Hi Allan,
Can ZFS use atomic_add_64() in the kernel for i386 instead of building
its own variant?
--HPS
On 2019-07-25 13:13, Peter wrote:
Hi Hans Petter,
glad to read You! :)
On Thu, Jul 25, 2019 at 09:39:26AM +0200, Hans Petter Selasky wrote:
! On 2019-07-25 01:00, Peter wrote:
! >>
On Thu, Jul 25, 2019 at 9:41 AM Trond Endrestøl
wrote:
>
> Hi,
>
> I have a VPN service running net/ocserv 0.12.4_1. Everything is ok
> until the first client disconnects. The main ocserv process hangs
> while destroying the tun interface, waiting indefinitely on
> "tun_cond".
>
> I ran an ocserv
Hi,
I have a VPN service running net/ocserv 0.12.4_1. Everything is ok
until the first client disconnects. The main ocserv process hangs
while destroying the tun interface, waiting indefinitely on
"tun_cond".
I ran an ocserv executable containing debug symbols through gdb and I
had a
Hi Hans Petter,
glad to read You! :)
On Thu, Jul 25, 2019 at 09:39:26AM +0200, Hans Petter Selasky wrote:
! On 2019-07-25 01:00, Peter wrote:
! >> The offending feature is either
! >> options ZFS
! >> or
! >> device dtrace
! >> (Adding any of these to the GENERIC config gives the same
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-07-21
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-07-15 to 2019-07-21.
During this period, we have:
* 1659
On 2019-07-25 01:00, Peter wrote:
Trying to compile my custom kernel in Rel. 11.3 results in this:
-- kernel.full ---
linking kernel.full
atomic.o: In function `atomic_add_64':
/usr/obj/usr/src/sys/E1R11V1/./machine/atomic.h:629: multiple definition of
`atomic_add_64'
10 matches
Mail list logo
