From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <725518204b6f4564c0a2569e655ac310@felloff.net> From: Charles Forsyth Date: Wed, 30 Nov 2016 15:34:57 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e0112c7f48bc5c305428672b5 Subject: Re: [9fans] create/create race Topicbox-Message-UUID: af92e67c-ead9-11e9-9d60-3106f5b1d025 --089e0112c7f48bc5c305428672b5 Content-Type: text/plain; charset=UTF-8 On 30 November 2016 at 15:28, Giacomo Tesio wrote: > I will use the new create syscall (without OEXCL support) when I need such > level of control and use ocreate with OEXCL Perhaps I'm confused. I thought OEXCL was just the same as the 9P create, which is what you were trying to get. With OEXCL set, it tries Tcreate; if that fails, it stops, and doesn't try open-with-truncate etc. --089e0112c7f48bc5c305428672b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 30 November 2016 at 15:28, Giacomo Tesio <giacomo@tesio.it> wrote:
I will use the new create sys= call (without OEXCL support) when I need such level of control and use ocre= ate with OEXCL

Perhaps I'm confused. I thought O= EXCL was just the same as the 9P create, which is what you were trying to g= et.
With OEXCL set, it tries Tcreate; if th= at fails, it stops, and doesn't try open-with-truncate etc.
--089e0112c7f48bc5c305428672b5--