On Fri, 02 Jul 2021 10:53:23 -0500, Scott Cheloha wrote: > As with sleep(3), usleep(3) is a wrapper around nanosleep(2). I'd > prefer it if we always call nanosleep(), even when the input is zero. > > This makes the code simpler, makes reasoning about behavior simpler, > and guarantees you get hit the ktrace for nanosleep if the program > calls usleep().
OK millert@ - todd
