From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1246 invoked by alias); 1 Mar 2017 10:49:52 -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: X-Seq: 40680 Received: (qmail 14737 invoked from network); 1 Mar 2017 10:49:52 -0000 X-Qmail-Scanner-Diagnostics: from new1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.221):SA:0(-0.4/5.0):. Processed in 1.183726 secs); 01 Mar 2017 10:49:52 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: psprint3@fastmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spf.messagingengine.com designates 66.111.4.221 as permitted sender) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=bqMOyCN8krY4lNaO1V1ESf+j0M0=; b=yNT00OmsHfgo9hfYq3F6X pLxQn7Xia6YnYuxiuKyjye7F8wrp8cEqU1e2+P7RZu2T6ea8ZSITdYoZAIj4FG2+ VacpKSsVtG9QrF9F2iGmCjkaQ0IqS+1qP+9GpQrG1hP6OtQCxL9I7+99Xtkj+hVH ip5Q6GRRSt2VfahtibJqA4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=smtpout; bh=bqMOyCN8krY4lNaO1V1ESf+j0 M0=; b=GR6QeeGwN3DuJiP5VIazZbO1OaAe7goAAvuRv/BG8huo5rKJ4G/VQGeD8 mA7AFnm3g1EQ0axPgUacUOamh652BessZmaf3P1+Doy2ZccicMis+3IWdtbqSoIM BPx5PaoornxoVoVDLv+H8l9HuthFdhSKy2POa+PbMjAuV9Hfms= X-ME-Sender: Message-Id: <1488365385.3896802.896627648.08162014@webmail.messagingengine.com> From: Sebastian Gniazdowski To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-715c2c0c Subject: Cannot write to zsystem flock's descriptor Date: Wed, 01 Mar 2017 02:49:45 -0800 Hello, # echo "test" > file # zsystem flock -t 0 -f MY_FD "file"; echo $? 0 # echo a>&${MY_FD} zsh: 11: bad file descriptor # exec {MY_FD}>&- (works, lock also works) I've added debug logs to system.c and there is: Read-write flags, 2 (O_RDWR) | 131072 (O_NOCTTY) = 131074 Before move fdflags 0 After move fdflags 0 After cloexec fdflags 1 lck.l_type RD:1, WR:3, is:3 So it looks good. When locking via "flock" util-linux program I can write to the FD. What could it be? if ((flock_fd = open(unmeta(args[0]), flags)) < 0) { flags are like first line of debug message. I think it's open() that matters. -- Sebastian Gniazdowski psprint3@fastmail.com