It should use 'demotion counter' everywhere.
Stuart Henderson <s...@spacehopper.org> wrote: > On 2021/02/01 14:32, Klemens Nanni wrote: > > On Mon, Feb 01, 2021 at 01:13:20PM +0000, Stuart Henderson wrote: > > > I think this needs documenting somewhere; I had to use the source to > > > remember what triggered "carpdemote 32" on some routers. I am open to > > > suggestions to improving the wording, the way I have it it's useful > > > as a reminder but isn't a great explanation for someone just learning > > > about it.. > > That reads fine to me as is and I agree it helps, thanks. > > > > > Index: pfsync.4 > > > =================================================================== > > > RCS file: /cvs/src/share/man/man4/pfsync.4,v > > > retrieving revision 1.36 > > > diff -u -p -r1.36 pfsync.4 > > > --- pfsync.4 30 Aug 2016 13:56:14 -0000 1.36 > > > +++ pfsync.4 1 Feb 2021 13:10:38 -0000 > > > @@ -130,6 +130,14 @@ Only run the pfsync protocol on a truste > > > dedicated to pfsync messages such as a crossover cable between two > > > firewalls. > > > .\" or specify a peer address and protect the traffic with > > > .\" .Xr ipsec 4 . > > > +.Pp > > > +.Nm > > > +will increase the > > > +.Xr carp 4 > > > +demote count for any interface groups associated with the interface > > OK kn with s/demote count/demotion counter/ as that is how at least all > > the demons call it (`man -k any=demot'). > > I deliberately used the same text as in ifconfig, so we have: > > bgpd/ospfd/ospf6d/ripd/relayd: demotion counter > sasyncd: demote counter > ifconfig: demote count > > I don't know which is best, but they should probably be united. > > > > > +by 32 during initialisation, and by 1 if the > > > +.Nm > > > +link is down or if a bulk update fails. > > > .Sh EXAMPLES > > > .Nm > > > and > > > > > >
