Re: PostgreSQL performance on FreeBSD

2016-06-25 Thread Maxim Sobolev
Sean, to the issue that you are describing it is also might be possible to do it some other way around. One, perhaps more portable, is to share a connected socketpair between two communicating processes, so that you can do non-blocking read on one of its ends from time to time and check if it

Re: New FreeBSD snapshots available: head (20160624 r302164)

2016-06-25 Thread Glen Barber
On Sat, Jun 25, 2016 at 02:13:24AM +, Glen Barber wrote: > New FreeBSD development branch installation ISOs and virtual machine > disk images have been uploaded to the FTP mirrors. > There have been a few reports of "missing" files on the FTP mirrors. This happened last week with the i386

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread Konstantin Belousov
On Sat, Jun 25, 2016 at 05:35:31PM +0200, Tijl Coosemans wrote: > On Sat, 25 Jun 2016 18:26:45 +0300 Konstantin Belousov > wrote: > > On Sat, Jun 25, 2016 at 05:17:14PM +0200, O. Hartmann wrote: > >> Is there a way to salvage the situation without relying on "customized" >

Re: panic with tcp timers

2016-06-25 Thread Randall Stewart
Ok Lets try this again with my source changed to my @freebsd.net :-) Now I am also attaching a patch for you Gleb, this will take some poking to get in to your NF-head since it incorporates some changes we made earlier. I think this will fix the problem.. i.e. dealing with two locks in the

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread O. Hartmann
Am Sat, 25 Jun 2016 17:35:31 +0200 Tijl Coosemans schrieb: > On Sat, 25 Jun 2016 18:26:45 +0300 Konstantin Belousov > wrote: > > On Sat, Jun 25, 2016 at 05:17:14PM +0200, O. Hartmann wrote: > >> Is there a way to salvage the situation without relying on

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread Tijl Coosemans
On Sat, 25 Jun 2016 18:26:45 +0300 Konstantin Belousov wrote: > On Sat, Jun 25, 2016 at 05:17:14PM +0200, O. Hartmann wrote: >> Is there a way to salvage the situation without relying on "customized" >> third party kernels? >> >> I usually use /bin/csh - so this might be of

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread Konstantin Belousov
On Sat, Jun 25, 2016 at 05:17:14PM +0200, O. Hartmann wrote: > Am Sat, 25 Jun 2016 14:35:44 +0300 > Konstantin Belousov schrieb: > > > On Sat, Jun 25, 2016 at 01:18:06PM +0200, O. Hartmann wrote: > > > Am Sat, 25 Jun 2016 10:02:38 +0300 > > > Konstantin Belousov

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread O. Hartmann
Am Sat, 25 Jun 2016 14:35:44 +0300 Konstantin Belousov schrieb: > On Sat, Jun 25, 2016 at 01:18:06PM +0200, O. Hartmann wrote: > > Am Sat, 25 Jun 2016 10:02:38 +0300 > > Konstantin Belousov schrieb: > > > > > On Fri, Jun 24, 2016 at 10:50:34PM +,

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread O. Hartmann
Am Fri, 24 Jun 2016 15:51:11 + Brooks Davis schrieb: > On Fri, Jun 24, 2016 at 06:00:19AM +0200, O. Hartmann wrote: > > Am Thu, 23 Jun 2016 21:07:51 + > > Brooks Davis schrieb: > > > > > Kernel config minimalists and those running aarch64 and

Re: svn commit: r302185 - head/release/doc/en_US.ISO8859-1/relnotes

2016-06-25 Thread Steffen Nurpmeso
Glen Barber wrote: |On Sat, Jun 25, 2016 at 03:02:11PM +0200, Steffen Nurpmeso wrote: |>| A selection of system daemons, including: |>| fingerd, |>| ftpd, |>|- rlogind, |>|- rshd, and |>|- sshd have been modified to support |>|+ rlogind, and |>|+

Cross-build Brokenness

2016-06-25 Thread Cy Schubert
It appears that the i386 cross-build is broken as follows. Builds on native amd64 are OK. --- main.o --- cc -target i386-unknown-freebsd11.0 --sysroot=/usr/obj/i386.i386/opt/src/svn -current/tmp -B/usr/obj/i386.i386/opt/src/svn-current/tmp/usr/bin -O2 -pipe -pipe -DRDUMP -g -MD

Re: Samba 4.3 and 4.4 crashes on FreeBSD 11-ALPHA4

2016-06-25 Thread Daniel Engberg
On 2016-06-25 12:16, Guy Yur wrote: > Hi, > > On Sat, Jun 25, 2016 at 12:20 PM, Konstantin Belousov > wrote: >> On Sat, Jun 25, 2016 at 11:49:39AM +0300, Konstantin Belousov wrote: >>> On Sat, Jun 25, 2016 at 01:03:13AM +0300, Guy Yur wrote:

Re: svn commit: r302185 - head/release/doc/en_US.ISO8859-1/relnotes

2016-06-25 Thread Glen Barber
On Sat, Jun 25, 2016 at 03:02:11PM +0200, Steffen Nurpmeso wrote: > |Author: gjb > |Date: Fri Jun 24 23:42:33 2016 > > Sigh. > > |Log: > | Update the release notes following r302182. > > | A selection of system daemons, including: > | fingerd, > | ftpd, > |- rlogind, > |-

Re: svn commit: r302185 - head/release/doc/en_US.ISO8859-1/relnotes

2016-06-25 Thread Steffen Nurpmeso
|Author: gjb |Date: Fri Jun 24 23:42:33 2016 Sigh. |Log: | Update the release notes following r302182. | A selection of system daemons, including: | fingerd, | ftpd, |- rlogind, |- rshd, and |- sshd have been modified to support |+ rlogind, and |+ rshd have

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread Konstantin Belousov
On Sat, Jun 25, 2016 at 01:18:06PM +0200, O. Hartmann wrote: > Am Sat, 25 Jun 2016 10:02:38 +0300 > Konstantin Belousov schrieb: > > > On Fri, Jun 24, 2016 at 10:50:34PM +, Brooks Davis wrote: > > > pipe(2) had an unnecessarily odd calling convention (ignoring the > > >

Re: panic with tcp timers

2016-06-25 Thread Randall Stewart
So All of our timers in TCP do something like - INFO-LOCK INP_WLOCK if (inp needs to be dropped) { drop-it } do other work UNLOCK-INP UNLOCK-INFO -- And generally the path “inp needs to be dropped” is rarely taken. So why don’t we change the procedure

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread O. Hartmann
Am Sat, 25 Jun 2016 10:02:38 +0300 Konstantin Belousov schrieb: > On Fri, Jun 24, 2016 at 10:50:34PM +, Brooks Davis wrote: > > pipe(2) had an unnecessarily odd calling convention (ignoring the > > argument the user thought they were passing and returning the two file >

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-25 Thread Mark Millard
On 2016-Jun-25, at 12:44 AM, Ngie Cooper wrote: > On Fri, Jun 24, 2016 at 9:50 PM, Mark Millard wrote: >> On 2016-Jun-24, at 2:50 PM, Alan Somers wrote: >> >>> As of r302180., the usr.sbin/rpcbind, sys/acl, and sys/sys/bitstring >>> tests should all be fixed. I opened PR

Re: Samba 4.3 and 4.4 crashes on FreeBSD 11-ALPHA4

2016-06-25 Thread Guy Yur
Hi, On Sat, Jun 25, 2016 at 12:20 PM, Konstantin Belousov wrote: > On Sat, Jun 25, 2016 at 11:49:39AM +0300, Konstantin Belousov wrote: >> On Sat, Jun 25, 2016 at 01:03:13AM +0300, Guy Yur wrote: >> > libtdb.so.1`tdb_runtime_check_for_robust_mutexes + 1475 at mutex.c:957 >>

Re: Samba 4.3 and 4.4 crashes on FreeBSD 11-ALPHA4

2016-06-25 Thread Konstantin Belousov
On Sat, Jun 25, 2016 at 11:49:39AM +0300, Konstantin Belousov wrote: > On Sat, Jun 25, 2016 at 01:03:13AM +0300, Guy Yur wrote: > > libtdb.so.1`tdb_runtime_check_for_robust_mutexes + 1475 at mutex.c:957 > > ... > > The pointer to tdb_runtime_check_for_robust_mutexes() appeared to be > most

Re: Samba 4.3 and 4.4 crashes on FreeBSD 11-ALPHA4

2016-06-25 Thread Konstantin Belousov
On Sat, Jun 25, 2016 at 01:03:13AM +0300, Guy Yur wrote: > libtdb.so.1`tdb_runtime_check_for_robust_mutexes + 1475 at mutex.c:957 > ... The pointer to tdb_runtime_check_for_robust_mutexes() appeared to be most useful, thanks. The two patches below should fix samba use of robustness. First,

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-25 Thread Ngie Cooper
On Fri, Jun 24, 2016 at 9:50 PM, Mark Millard wrote: > On 2016-Jun-24, at 2:50 PM, Alan Somers wrote: > >> As of r302180., the usr.sbin/rpcbind, sys/acl, and sys/sys/bitstring >> tests should all be fixed. I opened PR 210329 for the >> usr.bin/lastcomm

Re: HEADS UP: caution required with updates using custom kernels

2016-06-25 Thread Konstantin Belousov
On Fri, Jun 24, 2016 at 10:50:34PM +, Brooks Davis wrote: > pipe(2) had an unnecessarily odd calling convention (ignoring the > argument the user thought they were passing and returning the two file > descriptors via the two return registers). This required machine > dependent assembly for