zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
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>
Subject: Re: [BUG] zsystem:34: flock: invalid timeout value: '0'
Date: Sat, 27 Jun 2020 19:12:46 +0200	[thread overview]
Message-ID: <CAN=4vMo61Q0unbW6EMJAGmu3k-bUtzvdNWKgfvxAJQ4D-FxDaA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Zu0Xp2aW-7DTTvF8Ni_eSECzaWW4P=jgpPDNOT942v0g@mail.gmail.com>

On Sat, Jun 27, 2020 at 7:01 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Sat, Jun 27, 2020 at 12:27 AM Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
>>
>> Timeout strictly between 0 and 1 microsecond is not much different
>> from timeout between 1 and 2 microseconds. You can either round up or
>> down in both cases. 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. Let me try again.

Any implementation of sleep or timeout must round up. flock in zsh
doesn't round up but it must.

Roman.

  reply	other threads:[~2020-06-27 17:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 17:49 Sebastian Gniazdowski
2020-06-26 14:16 ` Daniel Shahaf
2020-06-26 19:42   ` Sebastian Gniazdowski
2020-06-27  1:47     ` Daniel Shahaf
2020-06-27  2:04       ` Bart Schaefer
2020-06-27  7:13         ` Cedric Ware
2020-06-27  7:27           ` Roman Perepelitsa
2020-06-27 17:01             ` Bart Schaefer
2020-06-27 17:12               ` Roman Perepelitsa [this message]
2020-06-27 17:58                 ` Bart Schaefer
2020-06-27 18:09                   ` Roman Perepelitsa
2020-06-27 20:38             ` Cedric Ware
2020-06-28  9:27               ` Roman Perepelitsa
2020-07-10 15:28                 ` Sebastian Gniazdowski
2020-07-11  5:18                   ` dana
2020-06-27 17:25           ` Sebastian Gniazdowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN=4vMo61Q0unbW6EMJAGmu3k-bUtzvdNWKgfvxAJQ4D-FxDaA@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=cedric.ware__bml@normalesup.org \
    --cc=d.s@daniel.shahaf.name \
    --cc=schaefer@brasslantern.com \
    --cc=sgniazdowski@gmail.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).