Re: unnbound vs file descriptors

2014-12-16 Thread Bogdan Andu
may just a naive question.. but did you sudo vipw and put unbound class for unbound user? /Bogdan On Tuesday, December 16, 2014 9:46 AM, Otto Moerbeek o...@drijf.net wrote: Hi, So i have started using unbound on a mailserver (running amd64 5.6-stable). First observation is that

Re: unnbound vs file descriptors

2014-12-16 Thread Otto Moerbeek
On Tue, Dec 16, 2014 at 09:04:52AM +, Bogdan Andu wrote: may just a naive question.. but did you sudo vipw and put unbound class for unbound user? That's not neccesary anymore these days, I believe. The rc.d subsystem takes case of setting the proper class, if available. At least it

Re: unnbound vs file descriptors

2014-12-16 Thread Antoine Jacoutot
may just a naive question.. but did you sudo vipw and put unbound class for unbound user? That's not neccesary anymore these days, I believe. The rc.d subsystem takes case of setting the proper class, if available. At least it That's correct. does not document setting the login

Re: Binary code patching and paravirtualization

2014-12-16 Thread Mark Kettenis
Date: Mon, 15 Dec 2014 23:21:35 +0100 (CET) From: Stefan Fritsch s...@sfritsch.de On Thu, 11 Dec 2014, Mark Kettenis wrote: From: Alexey Suslikov alexey.susli...@gmail.com Date: Thu, 11 Dec 2014 20:51:14 + (UTC) Stefan Fritsch sf at sfritsch.de writes: ---

Re: Dell R630 high interrupts on acpi0

2014-12-16 Thread Hrvoje Popovski
On 16.12.2014. 6:16, Jonathan Matthew wrote: On Sun, Dec 14, 2014 at 06:22:37PM +0100, Hrvoje Popovski wrote: Hi all, I have got two new Dell R630 and have current on them from Sun Dec 14 15:07:17. Installation went great and very fast. The problem is that I see around 11k interrupts on acpi0.

Re: divert(4) m_pullup

2014-12-16 Thread Mark Kettenis
Date: Mon, 15 Dec 2014 23:44:54 -0500 From: Lawrence Teo l...@openbsd.org Make divert_output() do an m_pullup only if truly needed. ok? Questionable. AFAIK m_pullup(9) will only do the pullup if it is necesary in the first place. Is there a measurable speedup from inlining the check?

Re: Dell R630 high interrupts on acpi0

2014-12-16 Thread Mark Kettenis
Date: Tue, 16 Dec 2014 15:16:58 +1000 From: Jonathan Matthew jonat...@d14n.org On Sun, Dec 14, 2014 at 06:22:37PM +0100, Hrvoje Popovski wrote: Hi all, I have got two new Dell R630 and have current on them from Sun Dec 14 15:07:17. Installation went great and very fast. The problem

Re: Binary code patching and paravirtualization

2014-12-16 Thread Mike Larkin
On Tue, Dec 16, 2014 at 11:08:03AM +0100, Mark Kettenis wrote: Date: Mon, 15 Dec 2014 23:21:35 +0100 (CET) From: Stefan Fritsch s...@sfritsch.de On Thu, 11 Dec 2014, Mark Kettenis wrote: From: Alexey Suslikov alexey.susli...@gmail.com Date: Thu, 11 Dec 2014 20:51:14 + (UTC)

Re: divert(4) m_pullup

2014-12-16 Thread Mike Belopuhov
On 16 December 2014 at 12:08, Mark Kettenis mark.kette...@xs4all.nl wrote: Date: Mon, 15 Dec 2014 23:44:54 -0500 From: Lawrence Teo l...@openbsd.org Make divert_output() do an m_pullup only if truly needed. ok? Questionable. AFAIK m_pullup(9) will only do the pullup if it is necesary in

Re: unnbound vs file descriptors

2014-12-16 Thread Otto Moerbeek
On Tue, Dec 16, 2014 at 10:30:21AM +0100, Antoine Jacoutot wrote: may just a naive question.. but did you sudo vipw and put unbound class for unbound user? That's not neccesary anymore these days, I believe. The rc.d subsystem takes case of setting the proper class, if available.

kmem readable kvm db

2014-12-16 Thread Ted Unangst
The kvm_bsd.db file only needs to be readable by programs that are setgid kmem. This is not much of an info leak since any user can read /bsd (or in many cases download a copy), but moving forward it would be nice to patch these leaks up one by one. A few kmem grovelers appear to still work

rand()/random() warning

2014-12-16 Thread Carlin Bingham
There is no warning when compiling code that calls random() but two warnings when compiling code that calls rand() - : warning: random() may return determinstic values, is that what you want?warning: rand() may return determinstic values, is that what you want? Is the first parameter to

Re: rand()/random() warning

2014-12-16 Thread Stuart Henderson
On 2014/12/17 09:37, Carlin Bingham wrote: There is no warning when compiling code that calls random() but two warnings when compiling code that calls rand() - I noticed this earlier as well. : warning: random() may return determinstic values, is that what you want?warning: rand() may

Re: Binary code patching and paravirtualization

2014-12-16 Thread Stefan Fritsch
On Mon, 15 Dec 2014, Ted Unangst wrote: On Mon, Dec 15, 2014 at 23:55, Stefan Fritsch wrote: Only in order to get a flags field that can be tweaked with config(8). And to allow disable via config(8), though that could also be achieved with a flag. Tweaking the behavior with a flags

Re: Binary code patching and paravirtualization

2014-12-16 Thread Alexey Suslikov
CVSROOT: /cvs Module name: src Changes by: s...@cvs.openbsd.org 2014/12/16 14:02:58 Modified files: sys/arch/amd64/amd64: identcpu.c sys/arch/amd64/include: specialreg.h Log message: Define and print HV cpuid flag. This is set by many hypervisors, including kvm, vmware, hyper-v. do they

Re: Dell R630 high interrupts on acpi0

2014-12-16 Thread Hrvoje Popovski
On 16.12.2014. 6:16, Jonathan Matthew wrote: We just got some r630s too, so I spent some time last week figuring out what's going on here. Something in the AML wants to talk to the intel MEI device. Normally this works, but on the new generation of dell machines (we've seen it on r630s and

Re: Dell R630 high interrupts on acpi0

2014-12-16 Thread Philip Guenther
On Tue, Dec 16, 2014 at 2:45 PM, Hrvoje Popovski hrv...@srce.hr wrote: on R630 i have custom bios settings and noticed that even if C states are disabled in bios i can see them in dmesg acpicpu0 at acpi0: C1 Uh, ACPI *requires* that C1 exist. The halt instruction is defined as entering C1, so

Re: Dell R630 high interrupts on acpi0

2014-12-16 Thread Frederic Nowak
Hi! The below diff extracts the memory range information from ACPI. It looks up all the memory ranges in _CRS and calculates minimal and maximal values for pci_machdep.c. I tested this on two amd64 machines and see no difference in pcidump. Do you think we need to keep the old method in case