From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3acfc358add926f6e589cb9faaf299fa@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p and how can I know when a write is finished
From: C H Forsyth <forsyth@vitanuova.com>
Date: Wed,  1 Mar 2006 15:57:18 +0000
In-Reply-To: <20060301152947.GB15178@wmii.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 076747f2-ead1-11e9-9d60-3106f5b1d025

>>Wrong, the Tclunk is not warranteed to arrive any time soon.
>>Tclunk != close()

> In the end you are on the safe side when waiting for Tclunk.

i think it's sad not to implement close [or equivalent] -> Tclunk in a timely way,
and indeed in an orderly manner (wrt the same client process),
at least for files, and especially for files with DMEXCL.