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 2039 invoked from network); 6 Jun 2020 15:10:22 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 6 Jun 2020 15:10:22 -0000 Received: (qmail 17673 invoked by alias); 6 Jun 2020 15:10:11 -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: 46008 Received: (qmail 23306 invoked by uid 1010); 6 Jun 2020 15:10:11 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot1-f46.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.210.46):SA:0(-1.9/5.0):. Processed in 1.661085 secs); 06 Jun 2020 15:10:11 -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.46 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=pYSnjJRbydKekbv9KR0ggyFrJQckcMdtxd/d85hVYJg=; b=hBk5DRcxmU1DFmBJ1icu2Ed/JdhLxtIMYC4EQE45urek2Eg1uKFLkzoIbfUC61lsHV DsvijwLeT054jVt8TJGWEofu+R3bW3ZgP9yEd1r4ypNJFRrPpsl5f+XYzYuzayh6ZOiH 12E035n9E4zm/7opyQ4CIufHkju2wg0665pb8KIHe7/URY1kjZai6+mt9RQJ0vbBHRMw cRORouZNaI2d1m9NbvhG0ueMbAAA5aDnfPGngxPZMt2r6u3x48ozFiuvcWzZt9p3TRr/ w46rRF7DUaJARxJFV+l+iLS3Ot3f/OU1skxCmTtAc3xXmS8LR7sCraewW5btvuGSVbTb 6rmQ== X-Gm-Message-State: AOAM533iXN7giHozcxUXFDl7eisrJjNjf+vypDS6iybZWy3hS6/nGVHr l28a7cToZTdlTo8HGBBJYmMzwjldw/DoUZXCWTl+kA== X-Google-Smtp-Source: ABdhPJyHj0KnUsDRG1eGwi3Tb6+jjnuMChbkwerC5GLRXjj5pNcbC1pBm1WmRqVGDGaXFp3l16x4FALZYv4rUtCsoDE= X-Received: by 2002:a9d:6349:: with SMTP id y9mr12204118otk.260.1591456175229; Sat, 06 Jun 2020 08:09:35 -0700 (PDT) MIME-Version: 1.0 References: <89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com> <94e73ebcf39d4d3f9c7ae257b1d75d16@CAMSVWEXC01.scsc.local> <20200605020748.635b9bb3@tarpaulin.shahaf.local2> <1941572212.466119.1591360860372@mail2.virginmedia.com> <13acd486e6457c1f708304026c3e1b59521ad328.camel@ntlworld.com> In-Reply-To: <13acd486e6457c1f708304026c3e1b59521ad328.camel@ntlworld.com> From: Bart Schaefer Date: Sat, 6 Jun 2020 08:09:24 -0700 Message-ID: Subject: Re: Any way to allow clobbering empty files when noclobber is set? To: Peter Stephenson Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" On Sat, Jun 6, 2020 at 4:58 AM Peter Stephenson wrote: > > Assuming both processes are actually doing clobbering opens (O_CREAT | > O_EXCL), you can't get into that position. Just to clarify: O_CREAT|O_EXCL is actually the NO_clobber-ing open. The clobbering open is just to open it for writing if allowed to. and start scribbling over whatever is there.