Jason McIntyre <[email protected]> wrote:

> On Tue, Oct 26, 2021 at 12:21:52PM +0000, Klemens Nanni wrote:
> > While designed to populate resolv.conf(5), there is nothing resolvd(8)
> > specific about the route message route(8) sends.
> > 
> > At least unwind(8) consumes and acts upon it;  there might as well be
> > other programs in ports that do such things, so describe it generically
> > while going into required detail for our selected base daemons.
> > 
> > OK?
> > 
> > NB:  I'll fix unwind.conf(5) wrt. `route nameserver' separately.
> > 
> 
> hi.
> 
> i think it sounds weird to talk about sending things without saying
> where they're going. maybe there is a better word than send? maybe this
> command is just recording, or specifying, or ...? i don;t have a good
> grasp of the process here.

"to the route socket"

Maybe rather than 'send', does it explain things better to say 'broadcast',


> > Index: route.8
> > ===================================================================
> > RCS file: /cvs/src/sbin/route/route.8,v
> > retrieving revision 1.101
> > diff -u -p -r1.101 route.8
> > --- route.8 22 Oct 2021 18:31:12 -0000      1.101
> > +++ route.8 26 Oct 2021 12:18:31 -0000
> > @@ -169,11 +169,16 @@ only changes in that routing table will 
> >  .Ar interface
> >  .Op Ar address ...
> >  .Xc
> > -Send a list of up to five nameserver address proposals to
> > -.Xr resolvd 8 .
> > +Send a list of up to five nameserver address proposals.
> > +.Pp
> > +.Xr unwind 8
> > +will learn them and act according to
> > +.Xr unwind.conf 5 .
> > +.Pp
> >  .Xr resolvd 8
> >  will replace all existing nameservers for the given interface in
> >  .Xr resolv.conf 5 .
> > +.Pp
> >  If no
> >  .Ar address
> >  argument is given, a request to remove the nameservers previously entered 
> > for
> > 
> 

Reply via email to