On 3/15/20 9:53 PM, Stuart Henderson wrote:
On 2020/03/15 19:05, Renaud Allard wrote:
On 15/03/2020 17:36, Stuart Henderson wrote:
Lots of churn again.. most of the new + are related to the new rpz and
serve-stale support. I've been running it for a few days with my usual
setup with no
On 2020/03/19 09:27, Renaud Allard wrote:
>
> After some days of testing I didn't see any real problem with that diff.
> It's working as expected.
>
> Also, I found out that putting "so-reuseport: no" completely stops all the
> stalling problems I had with unbound as a DoT server. It might be a
People are starting to capture kernel stack traces and produce
Flamegraphs. Those traces currently include the frames used by
dt(4) itself:
dt_pcb_ring_get+0x11d
dt_prov_profile_enter+0x6e
hardclock+0x1a9
lapic_clockintr+0x3f
Xresume_lapic_ltimer+0x26
acpicpu_idle+0x261
regress already uses them.
Feedback? OK?
Index: bt.5
===
RCS file: /cvs/src/usr.sbin/btrace/bt.5,v
retrieving revision 1.3
diff -u -p -r1.3 bt.5
--- bt.518 Mar 2020 20:19:42 - 1.3
+++ bt.519 Mar 2020
Move some more output functions to output.c and convert some other
functions to a fmt_xyz() function that returns a string with the value
instead of doing a printf(). This is mostly mechanical but please test.
--
:wq Claudio
Index: bgpctl.c
On Thu, Mar 19, 2020 at 07:25:05PM +0100, Martin Pieuchot wrote:
> A map contains (key, value) pairs. In that sense delete() deletes a
> pair. What about:
Correct, but I wanted to keep it short and therefore implied that
removing a key also removes the value.
> Delete the pair indexed by
On Thu, Mar 19, 2020 at 07:58:44PM +0100, Klemens Nanni wrote:
> Totally fine with me, just wanted to keep the diff clear, but I'll do so
> now before the manual grows further.
>
> OK?
>
hi. i think you need to end these descriptions with a full stop. you did
it with the last list item already!
Changing file permissions on /dev/dt to allow non-root access and a
simple `btrace -l' as non-root user already dt(4)'s KASSERT()s.
Instead of panicing the machine I think we can return early just like
in other failure cases and either allow the requested operation as
non-root (listing available
On Thu, Mar 19, 2020 at 07:07:10PM +, Jason McIntyre wrote:
> hi. i think you need to end these descriptions with a full stop. you did
> it with the last list item already!
Right, haven't done it for consistency with the other lists in there,
but then again function descriptions are proper
On 19/03/20(Thu) 17:43, Klemens Nanni wrote:
> Index: bt.5
> ===
> RCS file: /cvs/src/usr.sbin/btrace/bt.5,v
> retrieving revision 1.3
> diff -u -p -r1.3 bt.5
> --- bt.5 18 Mar 2020 20:19:42 - 1.3
> +++ bt.5 19 Mar
On Thu, Mar 19, 2020 at 08:17:10PM +0100, Klemens Nanni wrote:
> On Thu, Mar 19, 2020 at 07:07:10PM +, Jason McIntyre wrote:
> > hi. i think you need to end these descriptions with a full stop. you did
> > it with the last list item already!
> Right, haven't done it for consistency with the
In both command line usage and manual output format, find's options
and primaries behave the same, but their mdoc(7) markup is different and
therefore causes different tag names:
-x (option) can be looked up with ":tx" in the manual pager,
whereas -amin (primary) requires ":t-amin" including the
Claudio Jeker(cje...@diehard.n-r-g.com) on 2020.03.19 18:42:28 +0100:
> Move some more output functions to output.c and convert some other
> functions to a fmt_xyz() function that returns a string with the value
> instead of doing a printf(). This is mostly mechanical but please test.
>
ok
> --
13 matches
Mail list logo
