On Sat, Feb 10, 2018 at 01:12:59PM +1300, Theo Buehler wrote:
> On Fri, Feb 09, 2018 at 05:41:34PM -0600, Scott Cheloha wrote:
> > Hi,
> >
> > nanosleep(2) won't take more than 100 million seconds at a time,
> > so we ought to cap interval when we read it in. Otherwise, an
> > oversized interval
On Fri, Feb 09, 2018 at 05:41:34PM -0600, Scott Cheloha wrote:
> Hi,
>
> nanosleep(2) won't take more than 100 million seconds at a time,
> so we ought to cap interval when we read it in. Otherwise, an
> oversized interval argument causes iostat(8) to print as fast as
> it can.
>
> While here,
Hi,
nanosleep(2) won't take more than 100 million seconds at a time,
so we ought to cap interval when we read it in. Otherwise, an
oversized interval argument causes iostat(8) to print as fast as
it can.
While here, "interval" is called "wait" in the documentation when
the new syntax is in use,
