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=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1118 invoked from network); 27 Jun 2020 17:59:04 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 27 Jun 2020 17:59:04 -0000 Received: (qmail 28243 invoked by alias); 27 Jun 2020 17:58:56 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: Sender: zsh-workers@zsh.org X-Seq: 46150 Received: (qmail 24310 invoked by uid 1010); 27 Jun 2020 17:58:56 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot1-f53.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25850. spamassassin: 3.4.4. Clear:RC:0(209.85.210.53):SA:0(-1.9/5.0):. Processed in 1.740698 secs); 27 Jun 2020 17:58:56 -0000 X-Envelope-From: schaefer@brasslantern.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.210.53 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=9tMbquK4YBnsc4njn3AdyFbIt4kodYHoTEyUPzPxfP8=; b=omRGoRQXAE7s5F4jBHkpegS9bRTxo5Pa9KbzDheDwb+1tsj5nBYTQfvx/HkM4jU+TY LwJYVafO63r9qdrOgQSL3EvBR2qndc0HE+e3nN24ozQ6YQ8SOVV7NzgDRWOWruuzoF97 f9AD2pOXLJAnTkXqr3/6PuakQNWSrd6hC6BM75/qamNPGymmZQ1CvHLp7/vd0IcOROwG wzmSb+YVdczD0+yjE6E40AeI1fFZG6putVQKyMuW/aMEaTVpys+IN5yFrv+He75pBwyA embiMcVimRo1PyrOxtKXI9ILEcSLdUNq/TE3gXs9kembQOlfkrF0fv+fFA/YkXQ71Sxu xKGg== X-Gm-Message-State: AOAM531i0LlG05t8DISKdnLadYllAGNfMBL8wDQZbuqOMt6TrZtSIaR6 cv1do6HEQbeHRExJaAg0UTI5jcza/O+x61byaOZvHg== X-Google-Smtp-Source: ABdhPJzFOmZB24dbg9pXafLvvA9Yc6Q81shJNl4CM8Y5qjigovzh++9NyQJ8rVI0i82qKwEMKxj+tqMpWCn+Im8yM/Q= X-Received: by 2002:a05:6830:17ce:: with SMTP id p14mr7617928ota.161.1593280701804; Sat, 27 Jun 2020 10:58:21 -0700 (PDT) MIME-Version: 1.0 References: <20200626141644.7cb5e511@tarpaulin.shahaf.local2> <20200627014717.68986199@tarpaulin.shahaf.local2> <20200627071350.zqkdhzbk3mfej2tz@phare.normalesup.org> In-Reply-To: From: Bart Schaefer Date: Sat, 27 Jun 2020 10:58:10 -0700 Message-ID: Subject: Re: [BUG] zsystem:34: flock: invalid timeout value: '0' To: Roman Perepelitsa Cc: Cedric Ware , Daniel Shahaf , Sebastian Gniazdowski , Zsh hackers list Content-Type: multipart/alternative; boundary="0000000000004245d305a91492a0" --0000000000004245d305a91492a0 Content-Type: text/plain; charset="UTF-8" On Sat, Jun 27, 2020 at 10:12 AM Roman Perepelitsa < roman.perepelitsa@gmail.com> wrote: > On Sat, Jun 27, 2020 at 7:01 PM Bart Schaefer > wrote: > > > > On Sat, Jun 27, 2020 at 12:27 AM Roman Perepelitsa < > roman.perepelitsa@gmail.com> wrote: > >> > >> Rounding up is the right thing to do for sleeps > >> and timeouts because it allows you to provide a guarantee. > > > > I would be mildly surprised if this doesn't happen as part of the OS > implementation of the operation. > > I've a tendency to use an overly direct language that's often > perceived by others (especially Americans) as aggressive. Perhaps I > was overcautious this time. 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. --0000000000004245d305a91492a0--