On 2016/08/17 10:11, Peter Hessler wrote:
> It sure would be nice if we could see the PID of the process that added
> routes. Heck, route(8) even tries to print them already.
I haven't checked ifdefs so some of these might not need it, but easier to bump
them all. There's also the usual junk in g
> > > Index: net/if.h
> > > ===
> > > RCS file: /cvs/openbsd/src/sys/net/if.h,v
> > > retrieving revision 1.177
> > > diff -u -p -u -p -r1.177 if.h
> > > --- net/if.h 10 Jun 2016 20:33:29 - 1.177
> > > +++ net/if.h 1
On Wed, Aug 17, 2016 at 10:39:51AM +0100, Stuart Henderson wrote:
> On 2016/08/17 10:11, Peter Hessler wrote:
> > It sure would be nice if we could see the PID of the process that added
> > routes. Heck, route(8) even tries to print them already.
> >
> > Add the fields to the appropriate struct,
On 2016 Aug 17 (Wed) at 10:39:51 +0100 (+0100), Stuart Henderson wrote:
:On 2016/08/17 10:11, Peter Hessler wrote:
:> It sure would be nice if we could see the PID of the process that added
:> routes. Heck, route(8) even tries to print them already.
:>
:> Add the fields to the appropriate struct,
On 2016/08/17 10:11, Peter Hessler wrote:
> It sure would be nice if we could see the PID of the process that added
> routes. Heck, route(8) even tries to print them already.
>
> Add the fields to the appropriate struct, and while here, document which
> fields are in sync.
>
> (requested by krw@
It sure would be nice if we could see the PID of the process that added
routes. Heck, route(8) even tries to print them already.
Add the fields to the appropriate struct, and while here, document which
fields are in sync.
(requested by krw@)
OK?
Index: net/if.h
===
