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 7353 invoked from network); 4 Jun 2020 05:42:47 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 4 Jun 2020 05:42:47 -0000 Received: (qmail 2042 invoked by alias); 4 Jun 2020 05:42:37 -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: 45963 Received: (qmail 15603 invoked by uid 1010); 4 Jun 2020 05:42:37 -0000 X-Qmail-Scanner-Diagnostics: from mail-il1-f179.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.166.179):SA:0(-2.0/5.0):. Processed in 1.317632 secs); 04 Jun 2020 05:42:37 -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.179 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=T8WtL+xzl99Zh9YbNyUwyZDHyPBC/yWKvQb9V7nZ08Q=; b=QZrmqZMxbxwmknZJ7TYGB29tsaChB8h+jXdXm6JZaJ7+ymQU6GxRh3w62Ou4rN20QL vStIPj5ORcJ40mbntpokHj0D1W7bg7MUTRJDzbnK6Uy9y0KwtWEOSgLLcoEsnh9hbcGO atLgTUWIqjErMEzIonrHJjJmHIfao7zwXUcXd30zolqkUvYQoeCcS+yeabVBGHuSwwAq wP5uBtmTyCIvywMXK/EtjnENad1ju3rpu8c+cMDROe/HxjCa/uG+C+H5vf1cZOdRGLA+ bTBiZu6++D30Vq4pd68l+MzCrKFUQi1Cixc6teB8f9AWNIDuc7rN/YBqddvaGmGurR2s V2HQ== X-Gm-Message-State: AOAM531fIRQde1j4JiG+y+B7rrvgV/5uAyPuykwqZcpq5YEZA6CS50xb +8jPpr5uUab0vv5WiyVacWGzifdFvjfFaIXN8zZbG2H7 X-Google-Smtp-Source: ABdhPJw/+SuUiP71L7e8gyTGYct6oHfX3HZjROzxhdIlHhuUCJQeyHt0B+7qtFKj4Zd5Nm5EFECY0GS3IGgd1xiLrNo= X-Received: by 2002:a92:4899:: with SMTP id j25mr2820857ilg.168.1591249323467; Wed, 03 Jun 2020 22:42:03 -0700 (PDT) MIME-Version: 1.0 References: <89aed74d-db7b-47ad-b218-8158838049e9@www.fastmail.com> <94e73ebcf39d4d3f9c7ae257b1d75d16@CAMSVWEXC01.scsc.local> In-Reply-To: From: Roman Perepelitsa Date: Thu, 4 Jun 2020 07:41:52 +0200 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" The regular noclobber can use O_CREAT | O_EXCL to avoid races. How would any of the proposed modifications work? That is, how to implement unlink-if-empty without ever unlinking non-empty files? Or how to implement clobber-if-empty without ever clobbering non-empty files? Roman.