From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 19 Dec 2013 09:55:41 -0500
To: 9fans@9fans.net
Message-ID: <71f34c7f2a7fac1912f332bbdb14e2ac@brasstown.quanstro.net>
In-Reply-To: <CABwHSOstuGxuGObq=TYHVb=VzsvWrPnH_iShi_aRh5aCYXS5iA@mail.gmail.com>
References: <CABwHSOv=p17DeO_VHfY1DuX4H_h18eZ2qbVmCHyZrpd5NE6CVA@mail.gmail.com>
	<3e1e9e6fbfa856a01013a2f51b8d244f@coraid.com>
	<CABwHSOuTCu8HyLHis3ifWgF8harJ8rM2+8=Okr8cumk4BHS6CQ@mail.gmail.com>
	<34270f8ddb3fc06e71d4db496a891dd4@brasstown.quanstro.net>
	<CABwHSOstuGxuGObq=TYHVb=VzsvWrPnH_iShi_aRh5aCYXS5iA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] mk time-check/slice issue
Topicbox-Message-UUID: a0cd7cac-ead8-11e9-9d60-3106f5b1d025

> I was thinking about the problem and actually, at least in all
> circumstances I can think of, changing that one operation from <= to <
> would fix the problem.  If the times are on the same second, I would never
> have had time to change it.  This would fix the problem.  Perhaps this
> functionality can be controlled by an environment variable like NPROC.

i thought this idea might come up.  i think the reason not to do this
is a very fundamental principle: correctness.  never give up on correctness.

- erik