Stuart Henderson([email protected]) on 2017.09.13 12:27:40 +0100: > A user knowing that they want to provide services for slaac on > a network might do 'man -k slaac' and from the title and at least a > quick read of the manual it's not clear that this is the client side. > > I think it would be helpful for slaacd(8) to identify itself as a > client and at least hint that rtadvd can be used as the server side of > things, I'm not 100% happy with this diff but I think it's at least a > step in the right direction, does it seem reasonable to you or do you > have suggestions?
rtadvd(8) could refer to slaacd, and maybe both could refer to rfc4862? > > Index: slaacd.8 > =================================================================== > RCS file: /cvs/src/sbin/slaacd/slaacd.8,v > retrieving revision 1.3 > diff -u -p -r1.3 slaacd.8 > --- slaacd.8 23 Aug 2017 15:49:08 -0000 1.3 > +++ slaacd.8 13 Sep 2017 11:05:46 -0000 > @@ -20,7 +20,7 @@ > .Os > .Sh NAME > .Nm slaacd > -.Nd a stateless address autoconfiguration daemon > +.Nd a stateless address autoconfiguration client daemon > .Sh SYNOPSIS > .Nm > .Op Fl dv > @@ -77,6 +77,7 @@ socket used for communication with > .Sh SEE ALSO > .Xr hostname.if 5 , > .Xr ifconfig 8 , > +.Xr rtadvd 8 , > .Xr slaacctl 8 > .Sh STANDARDS > .Rs >
