On Tue, Feb 22, 2022 at 08:54:02PM +0000, Stuart Henderson wrote: > On 2022/02/22 17:45, Jason McIntyre wrote: > > On Tue, Feb 22, 2022 at 04:49:08PM +0100, Matthieu Herrb wrote: > > > Hi, > > > > > > It looks to me that the -Y option is used to specify the destination > > > to which to send synchronisation messages (not where to receive them, > > > this is -y). > > > > > > > hi. > > > > i've never used -Yy so may be wrong, but i think the text is trying to > > say that synctarget receives the messages (so the messages are sent to > > it). i don;t think it's wrong. but, well, i may be wrong ;) > > > > jmc > > > > > Index: dhcpd.8 > > > =================================================================== > > > RCS file: /cvs/OpenBSD/src/usr.sbin/dhcpd/dhcpd.8,v > > > retrieving revision 1.29 > > > diff -u -p -u -r1.29 dhcpd.8 > > > --- dhcpd.8 29 Aug 2017 08:20:18 -0000 1.29 > > > +++ dhcpd.8 22 Feb 2022 15:45:20 -0000 > > > @@ -252,7 +252,7 @@ the limited broadcast address (255.255.2 > > > .It Fl Y Ar synctarget > > > Add target > > > .Ar synctarget > > > -to receive synchronisation messages. > > > +to send synchronisation messages. > > > .Ar synctarget > > > can be either an IPv4 address for unicast messages > > > or a network interface name followed optionally by a colon and a numeric > > > TTL > > I understand the existing wording but it is a little awkward. > I don't think the direct s/receive/send/ change helps though. > Maybe this or something like it instead? > > Send synchronisation messages to > .Ar synctarget . > This can be either a destination IPv4 address for unicast messages > or a network interface name followed optionally by a colon and a numeric TTL > [...] >
yeah, that probably is clearer. jmc
