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 31884 invoked from network); 4 Jun 2020 20:36:26 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 4 Jun 2020 20:36:26 -0000 Received: (qmail 18387 invoked by alias); 4 Jun 2020 20:36:13 -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: X-Seq: 45971 Received: (qmail 23857 invoked by uid 1010); 4 Jun 2020 20:36:13 -0000 X-Qmail-Scanner-Diagnostics: from mail-oo1-f44.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25828. spamassassin: 3.4.4. Clear:RC:0(209.85.161.44):SA:0(-1.9/5.0):. Processed in 3.484459 secs); 04 Jun 2020 20:36:13 -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.161.44 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=cq4fieyrq0ZFdOIeJoM5KK3/nqsjkrqDWKc4KIBRaL0=; b=pOcyryt03UNGGeNd38z8oxa6GJA+R3hxpTKyzGCzNdS8JyPyDnUv1eriasyxzhb+Gz ipt8JHqTI2/lk/4ruhXAbCEuEFhIlFYaKA2uAHIS03Ad5vfLfZhJjZ4WPzHVvpv/FXMp 6CCQI5Cp/rk7ungrOBzQSIHzCp4sRzY4v02xvpU8Ys18z4wVP2tlRSaR7nao8icAHUvm UHoMpzPXSKA+CqGpwlhLBBeEilTWNql8eeN3GnVaRTSzqNTpjSJeIqSv9fmFIdOL7+lQ OdvRGd4EDZq5waPES6t+ZVINoodRoZdXxy48RsyE+ep9K7mClwjOztyyU6LjiCi2Hv/q H8Tg== X-Gm-Message-State: AOAM533SAOCOmIjK9a/5qeuh4XrCH4L6kL20SJ0X/ncAyBl1b7eyK9qK br4mmKuFRqBCMNCXex9k3l90xrBZf8PUiyjYEiCc9iNMxTNnLA== X-Google-Smtp-Source: ABdhPJyjXE9dM7PN9PAN9S6NuZp7H5kBHErcDEGs3uf8XiCRokWzPF+Q2Y1BjyULkBkpvL2lyxVb9sP8itsH2LffzFw= X-Received: by 2002:a4a:85c3:: with SMTP id u3mr5159143ooh.78.1591302933901; Thu, 04 Jun 2020 13:35:33 -0700 (PDT) MIME-Version: 1.0 References: <89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com> <94e73ebcf39d4d3f9c7ae257b1d75d16@CAMSVWEXC01.scsc.local> <99742213.429535.1591272937010@mail2.virginmedia.com> In-Reply-To: <99742213.429535.1591272937010@mail2.virginmedia.com> From: Bart Schaefer Date: Thu, 4 Jun 2020 13:35:22 -0700 Message-ID: Subject: Re: Any way to allow clobbering empty files when noclobber is set? To: "zsh-workers@zsh.org" Cc: Martin Tournoij Content-Type: text/plain; charset="UTF-8" On Thu, Jun 4, 2020 at 5:16 AM Peter Stephenson wrote: > > One thing I missed is that we already open the file and run fstat to > check if it's regular. We can simply check if it's empty at the > same point Exactly where my earlier question came from. > + if (isset(CLOBBEREMPTY) && buf.st_size == 0) > + { > + close(fd); > + return open(ufname, O_WRONLY | O_CREAT | O_TRUNC | O_NOCTTY, > + 0666); > + } Considering the concurrent-openers situation that Roman mentioned, I'm debating whether there is any benefit to doing: int newfd = open(ufname, O_WRONLY | O_CREAT | O_TRUNC | O_NOCTTY, 0666); close(fd); return newfd; I have a vague sense that keeping the descriptor open until the new file is created might prevent some races, but I can't recite an example.