On Thu, Dec 06, 2018 at 01:01:49PM -0500, Ted Unangst wrote:
> Jason McIntyre wrote:
> > On Thu, Dec 06, 2018 at 10:21:47PM +1100, Ross L Richardson wrote:
> > > 
> > > The number is in seconds, but that's currently not specified.
> > > 
> > > Wording which preserved "frequency" but made sense with "seconds"
> > > eluded me, so I changed things to refer to "interval".
> > > 
> > > 
> > > Ross
> > > ----
> > > 
> > > 
> > > Index: ifstated.conf.5
> > > ===================================================================
> > > RCS file: /cvs/src/usr.sbin/ifstated/ifstated.conf.5,v
> > > retrieving revision 1.13
> > > diff -u -p -r1.13 ifstated.conf.5
> > > --- ifstated.conf.5       18 Jun 2018 06:04:25 -0000      1.13
> > > +++ ifstated.conf.5       6 Dec 2018 11:12:44 -0000
> > > @@ -90,7 +90,8 @@ interfaces this equals the init state.
> > >  .Pp
> > >  In contrast to link state tests, external tests must be run periodically 
> > > to
> > >  evaluate their status.
> > > -The frequency at which an external test is run has to be set with the
> > > +The interval in seconds between invocations of an external test has to
> > > +be set with the
> > >  .Ar every
> 
> The interval in seconds between test runs is specified by the required keyword
> every.
> 

that would be fine too but a) why change frequency, it's not wrong and
b) a "test run" is, well, a test run. but not the same as an external
test.

i honestly think the author's original sentence was fine. it was just
missing the detail of measurement - seconds. the trick is to put that
back into the sentence with as little fuss as possible.

jmc

Reply via email to