From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED,
	FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 2454 invoked from network); 27 Jun 2020 18:10:40 -0000
Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2)
  by inbox.vuxu.org with ESMTPUTF8; 27 Jun 2020 18:10:40 -0000
Received: (qmail 29674 invoked by alias); 27 Jun 2020 18:10:32 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
Sender: zsh-workers@zsh.org
X-Seq: 46151
Received: (qmail 27301 invoked by uid 1010); 27 Jun 2020 18:10:32 -0000
X-Qmail-Scanner-Diagnostics: from mail-io1-f48.google.com by f.primenet.com.au (envelope-from <roman.perepelitsa@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.102.3/25850. spamassassin: 3.4.4.  
 Clear:RC:0(209.85.166.48):SA:0(-2.0/5.0):. 
 Processed in 3.595112 secs); 27 Jun 2020 18:10:32 -0000
X-Envelope-From: roman.perepelitsa@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.48 as permitted sender)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=XN1fSeAgmam/jJr4eVQj71o0UNPjMAuiy4Z6uA5Lk24=;
        b=ifk7wRiGSETVnlZWvo+ap4m5TPOUvVjIQ+UeVSHM6n1HULc7izfmoXShFDes9PcdRu
         IMP+2E+gKQWpGYZGgwnhWtSyTBads44dYKJd87LZReZamaWrgmWy/CCrZGrwJjWEOlUy
         iI8/sNe3/nwoZMerUb2Gi7MGJ25WheD8IkZkuPuFI2Na85hsWTc9t6aPjwFLI6wKnvjc
         wDnO1GBh/gAJBwqW3Fyh9JTOdUrcSDMbKq3VPRcspbH6Hhe1FdGR94+a0slLlLddWqpq
         cXFOQxOAD1sIZqp4ylFbj2wX08lRT9mykRJWgBnpMhlOX9336RRxxVHLbBlcRgHpSGCr
         PuDA==
X-Gm-Message-State: AOAM533l5rJG3kTy679A9TIjTCigYuIbqzuhduDprhDTZk4mO/BR2npU
	gT30ImBnX/Z23pB8pFaSP9PQ6Tf6pevXVcTY0Nc=
X-Google-Smtp-Source: ABdhPJyaggtDodmEEhdSZrhW9RMet7VAb0AAqmOkqOzAXuFmsdCSoVC5moB/LFOcAmfJ6r9gTzieg2gW0wdmOJfDEGo=
X-Received: by 2002:a5e:9b0e:: with SMTP id j14mr7963744iok.169.1593281396224;
 Sat, 27 Jun 2020 11:09:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAKc7PVAm3Wp9Gme42qNQeLo=QE8A2ZvcjcyQqw=aRQa2UDNX0w@mail.gmail.com>
 <20200626141644.7cb5e511@tarpaulin.shahaf.local2> <CAKc7PVCtHg1Pq1qBWBUwdiNe_8w9LXS_3t-2eBSuCg-ZoZnUgw@mail.gmail.com>
 <20200627014717.68986199@tarpaulin.shahaf.local2> <CAH+w=7YuMOOSbsgop53ZpCGQZ=COGBSS_nMAyS7m6aQ_YmpukA@mail.gmail.com>
 <20200627071350.zqkdhzbk3mfej2tz@phare.normalesup.org> <CAN=4vMpFpaQg03JbY_B3ktXAEmiUhXH4crdwyc1Ups8Cf=nf8A@mail.gmail.com>
 <CAH+w=7Zu0Xp2aW-7DTTvF8Ni_eSECzaWW4P=jgpPDNOT942v0g@mail.gmail.com>
 <CAN=4vMo61Q0unbW6EMJAGmu3k-bUtzvdNWKgfvxAJQ4D-FxDaA@mail.gmail.com> <CAH+w=7axxzO1ZuQ7MLjesXMA88pM0-0Lai2kPXUKhs6e7dy3NQ@mail.gmail.com>
In-Reply-To: <CAH+w=7axxzO1ZuQ7MLjesXMA88pM0-0Lai2kPXUKhs6e7dy3NQ@mail.gmail.com>
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Date: Sat, 27 Jun 2020 20:09:44 +0200
Message-ID: <CAN=4vMqKbCKRYGi3oAkOuWojaj8_uFu03bVgZ7k_2S=RhUS0Sg@mail.gmail.com>
Subject: Re: [BUG] zsystem:34: flock: invalid timeout value: '0'
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Cedric Ware <cedric.ware__bml@normalesup.org>, Daniel Shahaf <d.s@daniel.shahaf.name>, 
	Sebastian Gniazdowski <sgniazdowski@gmail.com>, Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"

>> On Sat, Jun 27, 2020 at 7:01 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> No, that's not it.  I just meant that the interval is ultimately implemented by calling nanosleep(), and I strongly suspect that nanosleep() rounds up.

I'm sure it does.

My point is that flock in zsh must not reject timeouts between 0 and 1
microseconds. The right thing to do when a timeout falls between two
steps of granularity is to round up. When converting any kind of
floating point timeout/deadline to integers, it's also necessary to
round up, never down.

Roman.