site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=g6jyQ4xUQhIXB8TpOJN+wAFIbcZmgWQK0RsXLNkCLkowD4HShdiw3qSYYZX9WQMrtzeRk3OwIr4zC2M1PV9x4XKfRSZLqtQ5YMNPxENILNx8VrlbcTPnhSAkZm74qcOT1vpzpigHFu9zjdU/dKjXQLnMF+GyFk9AvJZPt+7Ywao= On 11/30/05, Dave Yost <ListMailForDave@yost.com> wrote:

At 01:32 PM -0800 2005-11-29, Mark Day wrote:

...

On Nov 29, 2005, at 12:03 PM, darwin-dev-request@lists.apple.com wrote:

...

...

that's what sync(2) does.

It doesn't seem to.

Beware that sync(2) is an asynchronous call. It just begins the flushing of data to all volumes. If you're reading the disk immediately, the changes may not have been written yet.

Surely there should be a synchronous call one can use.

What happens after that synchronous call returns...? Are you expecting it to lock out the file system from any other access? It other words a synchronous call serves no purpose since at any moment another thread can come along and modify the state of the file system as long as it is mounted and writable. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com