On 8/16/2013 7:44 PM, Alexander Bluhm wrote:
On Wed, Aug 07, 2013 at 03:39:59AM +0200, Alexander Bluhm wrote:
Hi,
I have just removed a bunch of useless include netinet/in_var.h
from the machine independent drivers. I suspect that they are also
not needed in the architecture specific network d
On Wed, Aug 07, 2013 at 03:39:59AM +0200, Alexander Bluhm wrote:
> Hi,
>
> I have just removed a bunch of useless include netinet/in_var.h
> from the machine independent drivers. I suspect that they are also
> not needed in the architecture specific network drivers. Unfortunately
> I don't have
> Date: Thu, 15 Aug 2013 23:39:36 -0700
> From: Philip Guenther
>
> On Fri, 16 Aug 2013, Ted Unangst wrote:
> > As per http://research.swtch.com/macpprof
> >
> > We deliver all prof signals to the main thread, which is unlikely to
> > result in accurate profiling info. I think the diff below fix
On Fri, Aug 16, 2013 at 12:33, Mike Belopuhov wrote:
> On 16 August 2013 09:23, Ted Unangst wrote:
>> Actually, here's my concern. There's only one timeout for the process.
>> What happens when two threads are running on two CPUs? Is there a
>> guarantee that cpu0 will both set and execute the tim
On 16 August 2013 09:23, Ted Unangst wrote:
> Actually, here's my concern. There's only one timeout for the process.
> What happens when two threads are running on two CPUs? Is there a
> guarantee that cpu0 will both set and execute the timeout before cpu1
> sets it, or is there a race where cpu1
Hi,
in SNMPv3 engine id discovery is done by sending a noAuthNoPriv request
to the SNMP agent. The agent should reply with a usmStatsUnknownEngineIDs
report containing the authoritative engine id.
In case snmpd was configured with a minimum seclevel higher than none,
a usmStatsUnsupportedSecLevel
On Fri, Aug 16, 2013 at 12:23 AM, Ted Unangst wrote:
> On Thu, Aug 15, 2013 at 23:39, Philip Guenther wrote:
> > Making ITIMER_PROF per-thread like that matches neither what other OS's
> do
> > nor POSIX. jsing@ pinged about this last week and my comment then was
> > that this seems like a bug i
On Thu, Aug 15, 2013 at 23:39, Philip Guenther wrote:
> Making ITIMER_PROF per-thread like that matches neither what other OS's do
> nor POSIX. jsing@ pinged about this last week and my comment then was
> that this seems like a bug in signal delivery, not in the triggering of
> the profile timer:
On Thu, Aug 15, 2013 at 23:39, Philip Guenther wrote:
> opinions?
I knew if I made a broken diff I could trick you into fixing it right. :)
