From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: stdio and nfs-utils
Date: Wed, 25 Jul 2007 20:07:00 -0400
Message-ID: <20070726000700.GK7943@fieldses.org>
References: <20070725223723.GH7943@fieldses.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Neil Brown <neilb@suse.de>
In-Reply-To: <20070725223723.GH7943@fieldses.org>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Wed, Jul 25, 2007 at 06:37:23PM -0400, J. Bruce Fields wrote:
> I assume what's happening is that the stdio code is taking the error
> returns as a sign that it should leave the data in its buffer and just
> try again next time another fwrite adds more.  Does that make sense?
> I don't really understand how stdio is supposed to handle errors.

So I tried a test program that just does

	while (1) {
		fprintf(f, "%d\n", i++)
		fflush(f);
	}

and pointed it at one of those proc files, which will always return an
error on such a write.  On my fedora rawhide system, each write only
writes the new data.  On my debian sid system, each write writes all the
data accumulated so far.  Huh.

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs