fuse_parse_cmd_line.3 patch

2018-11-27 Thread Edgar Pettijohn III
remove a bunch of `_' where there shouldn't be `_'s Index: fuse_parse_cmd_line.3 === RCS file: /cvs/src/lib/libfuse/fuse_parse_cmd_line.3,v retrieving revision 1.2 diff -u -p -u -r1.2 fuse_parse_cmd_line.3 --- fuse_parse_cmd_line.3  

Re: option kcov + GENERIC.MP -> silent crash

2018-11-27 Thread Greg Steuck
I booted the patched kernel and it seems to have gone farther and I believe reached init before crashing. boot> b bsd.anton booting hd0a:bsd.anton: 12380226+2360336+270368+0+675840 [684182+128+754752+529898]=0x10d8f48 entry point at 0x1001000 [ using 1969992 bytes of bsd ELF symbol table ]

Re: top: allow reverse sort order

2018-11-27 Thread Klemens Nanni
On Wed, Nov 28, 2018 at 12:07:37AM +0100, Klemens Nanni wrote: > Note how an empty field is silently treated as the default field > "state", but that's an independent issue I'd like to address in a > separate diff for string_index(). Not a problem of string_index() actually. We consistently

Re: top: allow reverse sort order

2018-11-27 Thread Klemens Nanni
On Tue, Nov 27, 2018 at 03:52:52PM -0600, Scott Cheloha wrote: > > > static int > > > +getorder(char *field) > > > +{ > > > + rev_order = field[0] == '-'; > > > + > > > + return string_index(rev_order ? field + 1 : field, statics.order_names); > > > +} > > > + > > You need to check that the

Re: top: allow reverse sort order

2018-11-27 Thread Klemens Nanni
On Tue, Nov 27, 2018 at 11:28:31AM -0600, Scott Cheloha wrote: > No objections here to the feature in general. We already support reversing > select orderings in systat(1), which I've found useful in practice, so this > is not without precedent and is consistent with at least one other monitoring

Re: top: allow reverse sort order

2018-11-27 Thread Scott Cheloha
On Tue, Nov 27, 2018 at 11:28:31AM -0600, Scott Cheloha wrote: > On Sat, Nov 24, 2018 at 04:06:34PM +0100, Klemens Nanni wrote: > > Sometimes I want to see certain programs with least amount of memory, > > so this diff implements `o -field' to sort in reverse order. > > > > The logic is straight

mg: toggle-read-only-all

2018-11-27 Thread Mark Lumsden
Allow all non-ephemeral buffers to be toggled write/read-only. This toggle works while mg is running, unlike the -R option which is only during mg startup. ok? Index: buffer.c === RCS file: /cvs/src/usr.bin/mg/buffer.c,v retrieving

Re: top: allow reverse sort order

2018-11-27 Thread Scott Cheloha
On Tue, Nov 27, 2018 at 07:38:59PM +, Jason McIntyre wrote: > On Tue, Nov 27, 2018 at 11:28:31AM -0600, Scott Cheloha wrote: > > > @@ -137,13 +137,16 @@ mode. > > > This is identical to > > > .Em batch > > > mode. > > > -.It Fl o Ar field > > > +.It Fl o Oo - Oc Ns Ar field > > > Sort the

Re: top: allow reverse sort order

2018-11-27 Thread Jason McIntyre
On Tue, Nov 27, 2018 at 11:28:31AM -0600, Scott Cheloha wrote: > > @@ -137,13 +137,16 @@ mode. > > This is identical to > > .Em batch > > mode. > > -.It Fl o Ar field > > +.It Fl o Oo - Oc Ns Ar field > > Sort the process display area using the specified > > .Ar field > > as the primary key.

rad(8): auto discovered prefixes should not overwrite explicitly configured prefixes

2018-11-27 Thread Florian Obser
say you have 2001:db8:23::1/64 and fdac:23::1/64 configured on ix0 and the following rad.conf: interface ix0 { prefix fdac:23::/64 { autonomous address-configuration no } auto prefix { autonomous address-configuration yes } } rad should announce 2001:db8:23::/64 with the A

Re: bgpd refactor aspath_match a bit

2018-11-27 Thread Job Snijders
On Tue, Nov 27, 2018 at 06:23:53PM +0100, Claudio Jeker wrote: > On Tue, Nov 27, 2018 at 04:21:53PM +0100, Job Snijders wrote: > > On Fri, Nov 23, 2018 at 03:55:18PM +0100, Claudio Jeker wrote: > > > For origin validation I chacked the source_as in struct rde_aspath > > > this is not really the

Re: top: allow reverse sort order

2018-11-27 Thread Scott Cheloha
On Sat, Nov 24, 2018 at 04:06:34PM +0100, Klemens Nanni wrote: > Sometimes I want to see certain programs with least amount of memory, > so this diff implements `o -field' to sort in reverse order. > > The logic is straight forward: > > 1. merge common code from argument and command loops into

Re: bgpd refactor aspath_match a bit

2018-11-27 Thread Claudio Jeker
On Tue, Nov 27, 2018 at 04:21:53PM +0100, Job Snijders wrote: > Hi Claudio, > > On Fri, Nov 23, 2018 at 03:55:18PM +0100, Claudio Jeker wrote: > > For origin validation I chacked the source_as in struct rde_aspath > > this is not really the right place. It should be in struct aspath > > since

Re: bgpd refactor aspath_match a bit

2018-11-27 Thread Job Snijders
Hi Claudio, On Fri, Nov 23, 2018 at 03:55:18PM +0100, Claudio Jeker wrote: > For origin validation I chacked the source_as in struct rde_aspath > this is not really the right place. It should be in struct aspath > since that holds all the ASPATH related stuff. Change this, move > aspath_match out

Re: bgpd refactor community code

2018-11-27 Thread Job Snijders
On Thu, Nov 22, 2018 at 05:56:20PM +0100, Claudio Jeker wrote: > On Tue, Nov 13, 2018 at 06:53:55PM +0100, Claudio Jeker wrote: > > This is a large diff that changes the way communities are stored in > > filters and filter_sets. Both standard communities and large communities > > now share the

Re: refactor malloc a bit

2018-11-27 Thread Theo Buehler
On Mon, Nov 26, 2018 at 07:36:56AM +0100, Otto Moerbeek wrote: > Hi, > > this refactors the code that find an existsing allocation into a > separate function. The code is currently repeated in three spots. > > Prepatory work to get a somehwat more efficient version of the > "not-my-pool" case. >

Re: diff: ftpd(8): fix for sign-compare compiler warnings

2018-11-27 Thread Theo Buehler
On Sun, Nov 25, 2018 at 12:32:23AM +0100, Jan Klemkow wrote: > Hi, > > This diff fixes some -Wsign-compare compiler warnings in ftpd(8) by > using the right types for 'i' and 'len'. One warning is left, but I > don't see that it's fixable without suppressing the warning by a cast of > len to