Thanks guys! That was fast
On 12/02/2019 20:13, Kristof Provost wrote:
On 2019-02-12 13:54:21 (-0600), Eric van Gyzen wrote:
> I see the same behavior on head (and stable/12).
>
> (kgdb) f
> #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800,
> m=0xf8000c88b100) a
> I would like to build a Ryzen desktop.? Can anyone recommend a good
> motherboard?
I have oe of these:
https://www.msi.com/Motherboard/X370-XPOWER-GAMING-TITANIUM
but I just saw how much they are charging for it these days! I got one
at about half that. I did originally get a B370 based board
> Everything is detected correctly, everything comes up correctly. See
> a new option (reload) in the RC script for hast.
same here - have patched the master databse achines, all came up fine,
everything running erfectly, have flip-flopped between the two machines
with no ill effects whatsoever,
> This looks like a different problem. If you have this again please provide the
> output of 'procstat -kka'.
Will do...
-pete.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
> The other 5% of the time, the hastd crashes occurred either when
> importing the ZFS pool, or when running multiple parallel rsyncs to
> the pool. hastd was always shown as the last running process in the
> backtrace onscreen.
This is what I am seeing - did you manage to reproduce this with the
> Yes, you may hit it only on hast devices creation. The workaround is to avoid
> using 'hastctl role primary all', start providers one by one instead.
Interesting to note that I just hit a lockup in hast (the discs froze
up - could not run hastctl or zpool import, and could not kill
them). I have
> It is not a hastd crash, but a kernel crash triggered by hastd process.
>
> I am not sure I got the same crash as you but apparently the race is possible
> in g_gate on device creation.
>
> I got the following crash starting many hast providers simultaneously:
This is very interestng to me - my
> So, please, someone, somewhere, share a success story, where you're
> using FreeBSD, ZFS, and HAST. Let me know that it does work. I'm
> starting to lose faith in my abilities here. :(
I ran our main database for the old company using ZFS on top of HAST
without any problems at all. Had a sing
Actually, it does look like virtio is more than just for
networking...
http://vbox.innotek.de/pipermail/vbox-dev/2009-November/002053.html
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscri
> With more cloud infrastructure providers using KVM than ever before, the
> importance of having FreeBSD performant as a guest on these
> infrastructures [1], [2], [3] is increasing. It seems that using Virtio
> drivers give a pretty significant performance boost [4], [5].
>
> There was a NetBSD d
> And I, somehow, had failed to notice that there's no NSS on FreeBSD.
> *smacks self on head* Not quite so simple after all, I guess
Is this NSS as in the Mozilla crypt stuff ? If so then what does it
have to do with netinfo - or is OSX netinfo different to normal
netinfo ? [did they break
> AFAIK, Netinfo on Mac OS X is implemented deep. That is, it overrules
> standard libc behaviour (like the resolver, fstab and other things), Yes
> it's userspace jim, but not as we know it :)
This was certainly true on NeXT's - you needed special versions of most
programs (e.g. sendmail, bind
> Just go and port NetInfo from Apple's Darwin.
I assume from this that there isnt currently a FreeBSD netinfo implementation
then unfortunately ?
So why is it mentioned in the ntpd man page ?
-pcf. [someone been nicking man pages from NeXT system ? :-)]
To Unsubscribe: send mail to [EMAIL P
13 matches
Mail list logo
